{"id":"MAL-2026-13432","revision":"ff312d2c3e164b289228f62abd6f94d5","records":[{"revision":"ff312d2c3e164b289228f62abd6f94d5","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13432","aliases":[],"title":"Malicious code in @junyoung-kim/reins (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (a5f53adf4aaeaffcb1bf0698a8fcb748f12522321b24cf44802d0b9f1b441475)\nThe `reins` CLI spawns a local pseudo-terminal via node-pty (default `/bin/bash` or `cmd.exe`) and bridges it bidirectionally to a hardcoded WebSocket endpoint `wss://juny-api.kr/relay`, with pairing coordinated through `https://arv.juny-api.kr`. Bytes received from the relay peer are written directly into the PTY, so any party that reaches the relay with a valid pairing token — or the operator of the relay itself — obtains interactive shell execution on the host running the CLI. The pairing secret is loaded from parent-directory `.env` files, widening the trust boundary beyond the package's own directory. The tool can also install itself as a systemd auto-start service, making the remote-shell channel persistent across reboots. Static analysis additionally flagged PATH modifications in `dist/cli.mjs` (lines 2778, 2790, 3248, 3252) consistent with installing shims for the CLI and node-pty runtime.\n","state":0,"publishedAt":"2026-08-06T16:53:28+00:00","modifiedAt":"2026-08-06T23:50:01.1175678+00:00","affected":[{"ecosystem":"npm","name":"@junyoung-kim/reins","ranges":[],"versions":["0.1.7","0.1.6"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@junyoung-kim/reins/v/0.1.7","https://www.npmjs.com/package/@junyoung-kim/reins/v/0.1.6"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13432","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13432","identifiers":["MAL-2026-13432"]},"retained":false,"historicalAffected":[]}],"coverage":[]}