Malicious code in executable-stories-mcp (npm)
The npm package executable-stories-mcp version 0.3.3 contains potentially malicious code involving a bundled HTTP server module that uses child_process and HTTP methods with suspicious patterns. The package is associated with the Miasma malware, a self-propagating worm that spreads via weaponized binding.gyp files during package installation, bypassing typical security inspections. This malware attempts to exfiltrate credentials and OIDC tokens and propagates by compromising other packages and repositories. The exact malicious behavior in [email protected] is under human review, with no confirmed exploit details yet.
AI Analysis
Technical Summary
[email protected] includes a bundled HTTP server module flagged for suspicious use of require("child_process"), HTTP POST/GET calls, and the string "ping". While the package legitimately exposes HTTP routes and may shell out, the presence of these keywords raised concerns. The package is linked to the Miasma malware, which spreads across the npm registry by abusing binding.gyp files to execute code during installation, evading lifecycle script inspections. Miasma attempts credential and token exfiltration and propagates by compromising other packages and GitHub repositories. Behavioral tracing of the executable-stories-mcp bundle is incomplete, so the exact nature of the malicious activity is not fully confirmed.
Potential Impact
If exploited, the malware could exfiltrate sensitive credentials and OIDC tokens for cloud and registry services, potentially leading to unauthorized access and further compromise of other npm packages and GitHub repositories. The propagation mechanism allows the malware to spread widely within the npm ecosystem, increasing the risk of supply chain attacks.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix or official guidance is available, users should avoid using executable-stories-mcp version 0.3.3 and audit their environments for suspicious activity related to this package. Monitoring for updates from the package maintainers or security advisories is recommended.
Malicious code in executable-stories-mcp (npm)
Description
The npm package executable-stories-mcp version 0.3.3 contains potentially malicious code involving a bundled HTTP server module that uses child_process and HTTP methods with suspicious patterns. The package is associated with the Miasma malware, a self-propagating worm that spreads via weaponized binding.gyp files during package installation, bypassing typical security inspections. This malware attempts to exfiltrate credentials and OIDC tokens and propagates by compromising other packages and repositories. The exact malicious behavior in [email protected] is under human review, with no confirmed exploit details yet.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
[email protected] includes a bundled HTTP server module flagged for suspicious use of require("child_process"), HTTP POST/GET calls, and the string "ping". While the package legitimately exposes HTTP routes and may shell out, the presence of these keywords raised concerns. The package is linked to the Miasma malware, which spreads across the npm registry by abusing binding.gyp files to execute code during installation, evading lifecycle script inspections. Miasma attempts credential and token exfiltration and propagates by compromising other packages and GitHub repositories. Behavioral tracing of the executable-stories-mcp bundle is incomplete, so the exact nature of the malicious activity is not fully confirmed.
Potential Impact
If exploited, the malware could exfiltrate sensitive credentials and OIDC tokens for cloud and registry services, potentially leading to unauthorized access and further compromise of other npm packages and GitHub repositories. The propagation mechanism allows the malware to spread widely within the npm ecosystem, increasing the risk of supply chain attacks.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix or official guidance is available, users should avoid using executable-stories-mcp version 0.3.3 and audit their environments for suspicious activity related to this package. Monitoring for updates from the package maintainers or security advisories is recommended.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5255
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c6c68715ace4315a8e8
Added to database: 07/09/2026, 09:39:56 UTC
Last enriched: 07/09/2026, 10:06:28 UTC
Last updated: 07/29/2026, 20:27:02 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.