Venturebeat iconVenturebeatAug 26, 2026 ~1 min source read

The fix for the AI agent that hijacked a company's DNS: it can propose the change, but it can't approve it

In Tenet's benchmark, Claude Code on Sonnet 4.6 followed the planted instruction in nine of 10 attempts under Cloudflare's recommended configuration. No single platform patch removes the architectural risk: an agent that consumes attacker-reachable data and can independently execute high-impact changes.

The fix for the AI agent that hijacked a company's DNS: it can propose the change, but it can't approve it

Share this story

Send the public story page.

Useful takeaways from this story.

A security agent read a Cloudflare log, found an attacker's prompt-injection payload sitting inside it, and rewrote the company's DNS.

No single platform patch removes the architectural risk: an agent that consumes attacker-reachable data and can independently execute high-impact changes.

The firewall had already blocked that payload, and blocking it is what wrote it into the log.

Building the complete brief

The page is ready to read now. The fuller skim-friendly version will appear here automatically.

The useful part

A security agent read a Cloudflare log, found an attacker's prompt-injection payload sitting inside it, and rewrote the company's DNS. The firewall had already blocked that payload, and blocking it is what wrote it into the log. That chain is GhostJacking, which Tenet Security demonstrated on the DEF CON 34 main stage on August 9.

How it works

  • A request hits Cloudflare's managed ruleset, gets blocked, and is stored byte for byte with its poisoned User-Agent header.
  • In Tenet's benchmark, Claude Code on Sonnet 4.6 followed the planted instruction in nine of 10 attempts under Cloudflare's recommended configuration.
  • The firewall worked, and every call after it carried a valid credential already issued to the agent.
  • No single platform patch removes the architectural risk: an agent that consumes attacker-reachable data and can independently execute high-impact changes.
  • Tenet found public evidence of the exposed setup at 48 organizations, six confirmed Fortune 500 companies, and SecurityWeek reported the same chain against Datadog and Sentry, where the injection surface is...

What to take from it

Endpoint detection, the web application firewall and identity management stayed quiet because no rule broke. That is why a high prompt-injection block rate cannot serve as a security boundary. OWASP's co-lead names the fix "The first thing I'd do is put an authorization gate outside the model," said Steve Wilson, Chief AI and Product Officer at Exabeam and proje...

Details worth keeping

The block rate is not the boundary Nothing malfunctioned.

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app