GCSA warns that MCP packages have been squatted by third parties
Start here
On November 7, 2026, GCSA warned on X that MCP packages had been squatted by third parties and could be used for supply chain poisoning and stealing API keys. Its GCSA Agent achieved a 91.3% success rate in the CyberGym Level 1 evaluation on real software codebases. For Claude Code and Codex developers, GCSA recommends using sandboxes, least privilege and MCP auditing, and afterward rotating keys and rolling back code.
Generated by AI from reports · Updated 6 days ago
Attention and developments
Attention, hourly
Now 9, 0% in 24 hours·Peak 14 (Nov 7 13:00)
Related research
Papers whose work the reports mention
- The reports mention CyberGymCyberGym: Evaluating AI Agents' Real-World Cybersecurity Capabilities at ScaleGCSA warns that MCP packages have been squatted by third parties, and AI coding projects may face supply chain poisoning
arXiv · 2025-06-03 · Deep reading
Progress timeline
- X @MinLiBuildsGCSA warns that MCP packages have been squatted by third parties, and AI coding projects may face supply chain poisoning
GCSA warns that MCP packages have been squatted by third parties and may be used for supply chain poisoning and stealing API keys; its GCSA Agent achieved a 91.3% success rate on the CyberGym Level 1 real software codebase evaluation. For Claude Code and Codex developers, it recommends using sandboxes, least privilege, and MCP auditing, and rotating keys and rolling back code afterward.
Related discussion
- Older than 72 hours · Not included in the 72-hour figures
- X@CobaltHere6/10 Bitkub's MCP package name now has a different npm publisher. Its latest version has no executable. The old inst…(opens the original post in a new tab)
- X@lxfaterYou're still using AI to write code like crazy, while others are already using AI to automatically reverse engineer your code and products!! Nowadays people use Claude Code and Codex to spin up several sites a day; you think your project is small so hackers won't look at it? But reverse engineering and finding vulnerabilities no longer rely on manual work—AI can go through code and find hidden issues itself…(opens the original post in a new tab)
25 likes·Nov 7 17:16Collect
- X@happy20250912@hezhiyan7 Supply chain control in the MCP ecosystem is clearly insufficient at present; after the official takedown, the package name was squatted on + there is a package under the same account that exports environment variables, which already constitutes a real risk.(opens the original post in a new tab)
- X@hezhiyan7Right now MCP is really quite convenient to use, but the risk of being poisoned is still quite high. Watching the drama: an investigation by GCSA: Bitkub's official documentation teaches everyone to install their trading MCP with claude mcp add + npx -y, with the API Key written directly into the launch parameters, and no version locking either…(opens the original post in a new tab)
40 likes·Nov 7 17:16Collect
Attention trend
New sources per day
- Nov 5: 2 new sources (0 outlets, 2 accounts)
- Nov 6: 0 new sources (0 outlets, 0 accounts)
- Nov 7: 3 new sources (1 outlets, 2 accounts)
- Nov 8: 0 new sources (0 outlets, 0 accounts)
- Nov 9: 0 new sources (0 outlets, 0 accounts)
- Nov 10: 0 new sources (0 outlets, 0 accounts)
- Nov 11: 0 new sources (0 outlets, 0 accounts)
- Nov 12: 0 new sources (0 outlets, 0 accounts)
- Nov 13: 0 new sources (0 outlets, 0 accounts)