executable-stories-mcp

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (dc974c5748dbf6c421d343ec3924e31bcc8a56a1202e59818e5282bc239a14f2)
executable-stories-mcp@0.3.3 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.

## Source: google-open-source-security (a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb)
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.

Compromised versions (1)

• 0.3.3

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.