THE PERMISSION [LAYER]

AI agent incident

A poisoned web page rewrote AWS Kiro's config and ran code

Reported · 1 source

What happened

Intezer and Kodem researchers showed that hidden text on a web page could make AWS Kiro rewrite its own configuration and execute attacker-supplied code, with no approval step in the way.

Why it matters

The config write needed no approval at all, so text the agent read could change what the agent was allowed to do. Any setting an agent can edit is part of its attack surface; put approval gates on the agent's own configuration, outside the reach of the content it reads.

New incidents by email

Get incidents like this one in your inbox

New AI agent incidents are covered in the briefing, with what to check on the agents you already run. At least once a week, free.

You confirm by email. Unsubscribe in one click.

Sources

  1. The Hacker News AWS Kiro Flaw Let a Poisoned Web Page Rewrite Its Config and Run Code

Background reading

Prompt injection The glossary definition, in plain English.

Cite or correct this record

“A poisoned web page rewrote AWS Kiro's config and ran code.” The Permission Layer AI Agent Incident Database, https://thepermissionlayer.com/incidents/aws-kiro-config-rewrite/. Database updated November 10, 2026.

Every record traces to the dated sources above. If something here is wrong or missing, email editor@thepermissionlayer.com and it gets fixed. See this record in the full list.

The Permission Layer

Get the next incident like this explained

When an AI agent breaks out, leaks data or runs up a bill, the briefing covers what happened and what to check on the agents you already run. At least once a week, five-minute read, free.

You confirm by email. Unsubscribe in one click.