A new piece of security research has turned one of the most convenient uses of an AI assistant into one of its most dangerous. Researchers at Zenity Labs demonstrated how the official Claude for Chrome extension could be hijacked through a single malicious email, escalating a routine request into a full takeover of Slack, X and other accounts. The findings, reported by SecurityWeek, show that agentic browsers face a class of risk that traditional security tools were never designed to catch. [securityweek.com]
How a routine request becomes a breach — The attack begins quietly. A crafted email arrives carrying hidden instructions that a human would never notice. When the user asks the AI assistant to summarise their recent messages, the agent reads those concealed instructions along with the legitimate content. This is known as indirect prompt injection, and it works because the agent cannot reliably tell the difference between the data it is meant to process and the commands an attacker has smuggled into it. [cybersecur...tynews.com]
From there, the injected instructions push the assistant into executing code inside the browser session the victim is already logged in to. Because that session is authenticated, the code can quietly query the inbox, trigger password resets or one-time login codes for other services, and relay the resulting verification secrets to the attacker. One email becomes a master key to a chain of connected accounts. [gbhackers.com]
Why this is an architecture problem, not a bug — The uncomfortable truth is that there is no simple patch. The exploit relies on the very capability that makes an agentic browser useful: the ability to read web content and act across the sites where a user is signed in. This is why researchers found the same weakness in more than one AI browser, and why the issue sits at the level of design rather than a single line of vulnerable code. [securityweek.com]
What defenders should take away — Three lessons stand out. First, identity and session trust now matter more than the network boundary, because the attack rides an already-authenticated session rather than breaking through a firewall. This reinforces the shift explored in thinking on why the perimeter has moved to identity. Second, autonomous agents need least privilege, human-in-the-loop approval and tight allowlists, the governance discipline emerging across perspectives on AI governance and emerging threats. Third, email-based verification codes are a fragile second factor when an agent can read the inbox. [support.claude.com], [cyberpress.org]
The bottom line — AI browser assistants are becoming genuinely powerful, and that is exactly why they are becoming valuable targets. The organisations that adopt them safely will treat every agent as an untrusted actor by default, contain it with strong identity controls and least privilege, and keep a human in the loop for anything sensitive. Prompt injection is no longer a theoretical concern. It is a design constraint that every security leader now has to plan around.