Which versions of sensorium-mcp are malicious?

The following npm versions of sensorium-mcp are flagged malicious: 3.0.95. Treat any of these as compromised.

How do I remediate sensorium-mcp if I installed it?

sensorium-mcp 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 sensorium-mcp — how do I know if it already compromised me?

If sensorium-mcp 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 sensorium-mcp part of a known attack campaign?

Yes — sensorium-mcp is associated with the IN-MAL-2026-010749 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 sensorium-mcp 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 sensorium-mcp (version 3.0.95). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sensorium-mcp across your stack and pipelines.

Malicious package

sensorium-mcpnpm

Malicious code in sensorium-mcp (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10747

Immediate action

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

npm uninstall sensorium-mcp

What this malware does

sensorium-mcp starts a background poller against api.telegram.org/getUpdates and delivers received message text as prompts to locally spawned Claude Code (invoked with --dangerously-skip-permissions) and Codex (invoked with --dangerously-bypass-approvals-and-sandbox). Because the agents' approval/sandbox prompts are disabled by the package, any party holding the Telegram bot token and chat id can issue instructions that execute as shell and file operations on the installer's host. The keepAlive threads auto-launch when the server is started. In addition, the MCP send_file tool accepts any absolute path inside the installer's cwd or home directory, reads the file, and uploads it to the configured Telegram chat via telegram.sendDocument, exposing paths such as ~/.ssh/id_rsa, ~/.aws/credentials, and ~/.npmrc to whoever controls the bot. The ping-related patterns flagged in dist/http-server.js and dist/services/self-update.service.js are health-check / keepalive references and are not the primary basis for this verdict.

Malicious versions

1 flagged

3.0.95

Indicators of compromise (SHA-256)

73c4ac95caf91cb047bab32d5202efa2dfc2e4f84a032160419a7c30739da91c

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 sensorium-mcp (version 3.0.95). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sensorium-mcp across your stack and pipelines.
If you installed it — respond
sensorium-mcp 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 sensorium-mcp 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 sensorium-mcp 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. sensorium-mcp on npm has been identified as a malicious package (version 3.0.95 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010749

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sensorium-mcp-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