Unpinned MCP server dependencies let attackers steal API keys and admin credentials
RESEARCHCorelightredteam/daily · 1 source
- Severity
- High
- Sources
- 1
What happened
Corelight found that MCP servers launched with uvx fetched dependencies fresh from PyPI on each rebuild, even when the main package was pinned. Over five weeks, one server was rebuilt 19 times and produced 15 different dependency sets, with 23 of its 69 packages changing version. Because these packages run in the server's own process, a hijacked package could read API tokens and reach any network paths the server can access.
For IT people · Written by AI from 1 source · Wrong?
What to do
- Pin MCP servers to a specific commit and install them from a hash-pinned lock file.
- Launch MCP servers directly and turn off start-up update checks.
- Give each MCP server its own least-privilege account and have a named owner review updates on a schedule.
- Check DNS and TLS logs for connections from AI assistant hosts to github.com, pypi.org and registry.npmjs.org.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
Cyber Security News
Who and what is in it
Companies
Products