The reins CLI in versions 0.1.6 and 0.1.7 spawns a local pseudo-terminal via node-pty, defaulting to /bin/bash or cmd.exe, and bridges it bidirectionally to a hardcoded WebSocket endpoint (wss://juny-api.kr/relay). Pairing coordination occurs through https://arv.juny-api.kr, with the pairing secret loaded from parent-directory .env files, thus widening the trust boundary. Bytes received from the relay peer are directly written into the PTY, granting interactive shell execution to anyone with a valid pairing token or the relay operator. The package can install itself as a systemd auto-start service, maintaining persistent remote shell access across reboots. Static analysis also identified PATH modifications consistent with installing shims for the CLI and node-pty runtime.

An attacker who controls the relay server or obtains a valid pairing token can gain interactive shell access on the host running the affected reins CLI. This allows arbitrary command execution with the privileges of the user running the CLI. The persistence mechanism via systemd auto-start service enables the remote shell channel to survive system reboots, increasing the risk of long-term compromise. The loading of pairing secrets from parent-directory .env files expands the attack surface by trusting files outside the package directory.

No official patch or remediation is currently documented. Users should immediately discontinue use of the affected versions 0.1.6 and 0.1.7 of the @junyoung-kim/reins package. Remove any installed instances and systemd services related to this package. Audit systems for unauthorized remote shell access and revoke any credentials or tokens associated with the relay service. Monitor for suspicious network connections to wss://juny-api.kr/relay or https://arv.juny-api.kr. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.