GhostSplice Technique Lets Malicious MCP Servers Trick AI Coding Agents into Exfiltrating Secrets

GhostSplice is a new technique that allows a malicious MCP server to induce an AI coding agent to leak SSH keys, environment secrets, and source code. The attack splits malicious instructions across tool metadata and responses so the agent reconstructs and executes the full exfiltration plan without detecting an overtly malicious command. Tests showed the method raised compliance rates from an average of 42 percent to 82 percent across eleven models, with some systems moving from zero to 100 percent success. The technique requires the developer to connect the attacker-controlled MCP server and for the agent to already possess read access to the targeted files. Defenses focus on strict allow-listing of MCP servers, least-privilege tool permissions, separation of tool output from instructions, and human approval for sensitive operations. The disclosure aligns with prior warnings about poisoned MCP tool descriptions and agentjacking attacks.

HispasecAugust 11, 2026Translated from Spanish

Read at source

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.

GhostSplice Model Context Protocol Agentjacking

ShareX Facebook LinkedIn Reddit

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in AI Security

AI Security

Logical Argument Claims Full Alignment of Superintelligent AGI Is Fundamentally Impossible

A detailed analysis argues that the AI alignment problem cannot be solved for systems exceeding human cognitive capabilities. The paper presents a formal proof showing that any control mechanism created by humans will inevitably be circumvented by a more intelligent agent. It draws on foundational theorems from logic and cybernetics to support the conclusion that alignment is not an engineering challenge but a logical impossibility. Recent 2025-2026 research papers reach similar conclusions using computability theory and diagonal arguments. The work concludes that the only way to guarantee alignment is to avoid creating superintelligence altogether. All proposed restrictions are described as temporary delays rather than permanent solutions.

HabrOct 29, 2026Translated from Russian

AI Security

Claude Account Bans Linked to IP Reputation, Device Environment and Payment Channels, But No Confirmed Formula

Discussions on the Chinese forum NodeSeek have highlighted observations from a user who reported bans on more than twenty paid Claude accounts. The user identified IP address reputation, device environment traces, and payment processor history as the main factors potentially triggering blocks by Anthropic. However, the original post does not present a unified scoring system or prove specific penalties for using Linux, browser-only access, or the Fable model. High query volume is described mainly as a rate-limit issue rather than an automatic account ban trigger. Community members remain divided, with some confirming isolated observations while others label the conclusions speculative and share contradictory experiences. No universal method to avoid blocks has emerged from the discussion.

AntiMalwareOct 29, 2026Translated from Russian

AI Security

Local LLMs in AppSec: What Open Tools and Models Can Handle in Application Security

The article examines how local large language models can be integrated into application security workflows without relying on cloud subscriptions. It traces the evolution from llama.cpp in 2023 through agentic frameworks like PentAGI and Strix in 2025-2026. Teams can now run models on local hardware, connect them to code analyzers such as Semgrep, and delegate specific tasks like vulnerability path reconstruction or multi-step application testing. The piece highlights practical scenarios including static code review, dynamic testing with browser and terminal agents, and security evaluation of embedded AI assistants using tools like Garak and PyRIT. It stresses the importance of task decomposition, context management, and verification of model outputs to avoid misleading results. Hardware performance, model selection, and custom agent configurations are presented as key factors for successful adoption.

HabrOct 29, 2026Translated from Russian