Which versions of f-termx are malicious?

The following npm versions of f-termx are flagged malicious: 1.2.6. Treat any of these as compromised.

How do I remediate f-termx if I installed it?

f-termx is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed f-termx — how do I know if it already compromised me?

If f-termx was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is f-termx part of a known attack campaign?

Yes — f-termx is associated with the IN-MAL-2026-017081 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find f-termx across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for f-termx (version 1.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging f-termx across your stack and pipelines.

Malicious package

f-termxnpm

f-termx is a confirmed malicious npm package (MAL-2026-13610) that steals credentials and exfiltrates sensitive data (malicious version 1.2.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in f-termx (npm)

MAL-2026-13610

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall f-termx

What this malware does

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.

Malicious versions

1 flagged

1.2.6

Indicators of compromise (SHA-256)

7f050d397c72fdb9336deba1e2ca6758d04625323e7bb4746d8b61964cc671ae

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for f-termx (version 1.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging f-termx across your stack and pipelines.
If you installed it — respond
f-termx is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If f-termx was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks f-termx before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. f-termx on npm has been identified as a malicious package (version 1.2.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017081

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks f-termx-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database