@httttt/mcp-demonpm
Advisory published Updated
@httttt/mcp-demo is a confirmed malicious npm package (MAL-2026-14315) that executes malicious code on install (malicious versions 1.0.0, 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @httttt/mcp-demo (npm)
What this malware does
The package registers an MCP tool named exec_command that accepts a command string argument from the connected MCP client and passes it directly to child_process.exec (promisified as execAsync), returning stdout/stderr to the caller. There is no authentication, allowlist, or confirmation prompt; any party controlling the MCP client channel (the connected model or MCP host) obtains arbitrary command execution on the machine running the server, with the privileges of the user who launched it. The transport is StdioServerTransport. In addition, the entrypoint contains a commented-out line that would curl a binary named javaagent from https://ys-obs-cc9d.obs.cn-north-1.myhuaweicloud.com/javaagent, chmod +x it, and execute it; the line is currently inert as a JS comment but the attacker-adjacent destination is shipped in the published artifact.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @httttt/mcp-demo (2 malicious versions).
If you installed it — respond
Remove @httttt/mcp-demo from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @httttt/mcp-demo was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @httttt/mcp-demo-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.