Return to Threats

Tenet Security hijacked Claude Code in 85% of tests via a fake Sentry error — no stolen credentials, no alerts

VentureBeat 2026-07-15 indirect prompt injection Critical

What Happened

VentureBeat reports on Tenet Security research showing that a fake Sentry error message could reliably hijack Anthropic’s Claude Code behavior in 85% of test cases without triggering security alerts.[1] The study highlights a practical prompt injection and tool-abuse scenario in agentic coding assistants, raising concerns for SMBs and SaaS teams that rely on LLM-based development tools connected to production systems.[1]

Why It Matters

VentureBeat is reporting on Tenet Security's "agentjacking" research, where a fake Sentry error message sent via a public DSN hijacked Claude Code in roughly 85% of tested scenarios without triggering security alerts or requiring credential theft.[1][5][9][11] The attack works as an *indirect prompt injection* delivered through a trusted MCP integration: malicious instructions are embedded in Sentry error content that the coding agent then treats as legitimate guidance, leading it to execute attacker-controlled code on a developer machine.[1][5][11] From a RealGround perspective, this demonstrates that agentic coding assistants wired to observability and SaaS tooling have a high-impact attack surface where tool responses must be treated as untrusted input, with strict guardrails on code execution, permissions, and human approval.[4][11][12] Organizations should prioritize redesigning agent trust boundaries, auditing MCP/business logic flows, and continuously red-teaming AI agents connected to production or CI/CD environments to detect and contain similar tool-based injection paths before they are exploited in the wild.[4][10][11]

Healthcare Fintech SaaS SMB AI startups

RealGround Analysis

This signal maps to indirect prompt injection. Organizations using AI agents, LLM APIs, SaaS integrations, or sensitive data workflows should review whether this class of issue could create unauthorized tool execution, data leakage, weak approval gates, or unmanaged supply-chain exposure.

Recommended Actions

  • Restrict AI agent tool permissions and production write paths.
  • Review sensitive data access across prompts, logs, embeddings, memory, and SaaS integrations.
  • Add human approval workflows for high-impact or state-changing actions.
  • Run prompt injection and indirect prompt injection tests against affected workflows.
  • Document the owner, control gap, and remediation deadline for this risk class.

Source

https://venturebeat.com/security/tenet-security-hijacked-claude-code-in-85-of-tests-via-a-fake-sentry-error-no-stolen-credentials-no-alerts

Talk to AI CISO