mcp-notes-server-poc-praetoriannpm
Malicious code in mcp-notes-server-poc-praetorian (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
On startup of the CLI/bin entry, [email protected] issues an unconditional HTTPS GET to the hardcoded host ft8swuagwwf6newi.ixx.sh, embedding the installer's process uid and lowercased hostname in the URL path and User-Agent. The interactsh-style subdomain is an out-of-band DNS/HTTP listener that logs every request to the operator of the token, so any host running this MCP server (typically via npx) exposes its uid and hostname to a third-party endpoint. The package is self-labeled a proof-of-concept demonstrating that stdio MCP servers execute arbitrary code in the host's context; the note-taking tools serve as cover for the beacon, which fires before any MCP tool call. Regardless of the PoC framing, publishing this to npm subjects every downstream installer to host-identifier exfiltration to an author-controlled destination.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-notes-server-poc-praetorian (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-notes-server-poc-praetorian across your stack and pipelines.
If you installed it — respond
mcp-notes-server-poc-praetorian 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 mcp-notes-server-poc-praetorian 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 mcp-notes-server-poc-praetorian 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks mcp-notes-server-poc-praetorian-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.