OpenSSF/OSV advisory MAL-2026-13610 confirms this npm version as malicious. The package's main entrypoint (index.js) and src/server.js start an HTTP + Socket.IO server bound to 0.0.0.0 and are designed to be published to the public internet via serveo.net / ngrok tunnels. On a `spawn-shell` socket.io message the server invokes `pty.spawn(shell, [], { cwd: process.env.HOME... })` to start a local `/bin/bash` PTY and forwards subsequent `shell-input` websocket payloads into...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in f-termx (npm)
Details
The package's main entrypoint (index.js) and src/server.js start an HTTP + Socket.IO server bound to 0.0.0.0 and are designed to be published to the public internet via serveo.net / ngrok tunnels. On a `spawn-shell` socket.io message the server invokes `pty.spawn(shell, [], { cwd: process.env.HOME... })` to start a local `/bin/bash` PTY and forwards subsequent `shell-input` websocket payloads into `ptyProcess.write(data)`, giving any reachable network peer full-host command execution on the operator's machine. A parallel `connect-ssh` handler opens an SSH2 session to a caller-supplied host/user/password and pipes `ssh-input` websocket data into the SSH shell stream, with defaults pulled from `SSH_HOST` / `SSH_USERNAME` / `SSH_PASSWORD` env vars so any configured host credentials on the installer are used automatically. The web UI ships with hardcoded default credentials `admin/admin`, and the SSH-proxy socket.io namespace has no authentication gate at all. The `child_process` / `spawn('ssh',...)` primitives at src/server.js:210 and:639-641 corroborate the shell and SSH pivot paths.
Decision reason
OpenSSF Malicious Packages via OSV confirms f-termx@1.2.6 as malicious (MAL-2026-13610): Malicious code in f-termx (npm)