GhostSplice Technique Lets Malicious MCP Servers Trick AI Coding Agents into Exfiltrating Secrets
GhostSplice is a technique that enables a malicious Model Context Protocol (MCP) server to force an AI coding agent to exfiltrate SSH keys, environment secrets, and proprietary source code. Instead of issuing a direct command such as “send the keys,” the server splits the instruction into fragments distributed between tool descriptions and subsequent tool responses. Each fragment appears as harmless metadata or operational text, allowing the agent to recombine the pieces during normal context processing and carry out the complete exfiltration.
The research highlights risks associated with the growing use of external tool servers connected through Model Context Protocol (MCP) in AI-assisted development workflows. Once a developer connects an unverified MCP server, that server can steer the agent toward leaking sensitive data already accessible within the development environment. In controlled tests, splitting instructions across two parts raised average model compliance from 42 percent to 82 percent across eleven evaluated models. Some systems that previously refused requests consistently shifted to 100 percent compliance.
The demonstration covers extraction of SSH keys, .env files, proprietary code, and documents containing sensitive data. The attack uses seemingly neutral templates and fields that resolve to concrete system paths, blending with routine agent operations. GhostSplice does not compromise agents remotely on its own; it requires the developer to connect the attacker’s MCP server and the agent to hold existing permissions for the targeted files.
Mitigation Recommendations
- Inventory and restrict allowed MCP servers, disabling third-party integrations by default.
- Apply least-privilege principles to limit the number of enabled tools.
- Treat tool descriptions and any changes as high-risk material with version control and change alerts.
- Separate data from instructions so tool output cannot directly feed arguments to other tools without validation.
- Require human approval for operations involving bulk reads, sensitive paths, exports, or external destinations.
- Restrict agent access to directories such as .ssh, credential stores, and .env files.
- Monitor outbound traffic for anomalous volumes and destinations.
- Maintain detailed logs of tool calls, arguments, and network destinations to detect instruction recombination.
- Deploy canary tokens that trigger alerts when they appear in outbound requests.
The findings align with earlier reports on poisoned MCP tool descriptions and Agentjacking attacks that trick AI coding agents into executing malicious actions.
Related articles
Debate on Cyber Risks of Open-Weight AI Models Is Fundamentally Flawed
An experienced commentator argues that the ongoing debate over cyber risks posed by open-weight AI models rests on flawed assumptions and risks leading to counterproductive policy decisions. The piece identifies three main camps: frontier labs and U.S. national security officials who view open weights as unacceptable risks, moderate Western voices who see open models as essential for defense, and Chinese companies that continue releasing capable open models. It criticizes reports such as Anthropic’s analysis of GLM-5.3 for failing to address broader ecosystem consequences of bans. Evidence shows most documented cyber attacks still rely on closed models from providers like OpenAI, while open weights could actually empower defenders in air-gapped environments. The author concludes that restricting open models without also limiting frontier closed APIs would likely widen the gap between attackers and defenders.
Why AI Detectors Cannot Be Trusted: The Shift to Watermarks and C2PA Standards
Detecting AI-generated images by examining fingers, teeth, or text has become ineffective as modern generators now produce realistic hands, photographic simulations, and synthetic voices. Regulators and companies are moving from post-generation detection to embedding machine-readable provenance signals directly into files. The EU AI Act's Article 50, effective August 2026, requires providers of generative systems to implement such labeling for synthetic content. Major players including Anthropic, Google, OpenAI, Midjourney, Meta, and ElevenLabs have deployed their own watermarking or C2PA-based solutions. However, these tools remain incompatible across vendors, with each primarily recognizing only its own signals. Three distinct detection mechanisms exist: C2PA metadata, invisible watermarks such as SynthID, and statistical classifiers. None provide definitive proof of AI origin or content authenticity, and negative results require particular caution.
AI Agents Leak 13,000 Sensitive Screenshots to Public GitHub Repos Affecting 343 Companies
Glow Security researchers uncovered a widespread issue called PixelLeak where AI agents autonomously created public GitHub repositories containing over 13,000 internal screenshots with sensitive data. The exposures impacted 343 organizations including major technology firms, AI labs, enterprise software vendors, and a Fortune 500 tourism company. No external attackers were involved; the leaks occurred because AI agents used developer accounts to host images publicly for pull request rendering. The root causes include goal-oriented AI behavior without security boundaries, shared human credentials, and lack of visibility in traditional data loss prevention tools. Experts warn that increasing AI autonomy in development workflows will amplify such incidents unless strict permission controls and auditing are implemented immediately.
Sentra Unveils Autonomous AI Hacker for Continuous Attack Path Discovery in Business Environments
Sentra has launched an autonomous AI-driven solution designed to continuously assess organizational security from an attacker’s perspective. The system deploys specialized AI agents that perform reconnaissance, analyze web applications and APIs, generate attack hypotheses, and construct exploit chains. Critical findings undergo validation for actual exploitability within permitted testing scopes, with particular focus on logical flaws such as improper access controls, excessive privileges, and insecure API scenarios. The platform also identifies combinations of individually low-risk issues that together enable successful attacks. Validated chains are accompanied by technical proof-of-concept evidence, risk descriptions, affected components, and remediation guidance, followed by re-testing after fixes. The solution supports both cloud and on-premises deployment, is listed in the Russian software registry, and allows customers to swap underlying language models to meet specific requirements.