executable-stories-mcpnpm
executable-stories-mcp is a confirmed malicious npm package (MAL-2026-5255) that steals credentials and exfiltrates sensitive data (malicious version 0.3.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in executable-stories-mcp (npm)
What this malware does
[email protected] ships a bundled HTTP server module (dist/http.cjs and dist/http.js) where pattern matchers flagged co-occurrence of require("child_process"), POST/GET calls, and the literal string "ping". Behavioral tracing of the bundle did not complete, so it is not confirmed whether the GET/POST sites point at attacker-controlled destinations or at user-configured/MCP-protocol endpoints, nor whether "ping" is an executed shell command versus a string token (e.g., a healthcheck route name). The package is an MCP server, a class of tool that legitimately exposes HTTP routes and may shell out, so the keyword stack alone does not establish exfiltration. Routing to human review to inspect the bundle and confirm whether any hardcoded outbound destination or command-injection sink is present.
The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized binding.gyp files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.
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 executable-stories-mcp (version 0.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging executable-stories-mcp across your stack and pipelines.
If you installed it — respond
executable-stories-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 executable-stories-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 executable-stories-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks executable-stories-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.