Short answer
An AI browser agent can navigate sites, fill forms and click buttons for you, and Anthropic says every web page it visits is a potential attack vector. Hidden instructions on a page can steer it, and no browser agent is immune. Limit what it can reach, stay logged out of sensitive accounts, and approve payments and sends yourself.
Key takeaways
- Anthropic says every web page a browser agent visits is a potential vector for prompt injection, and that browser agents can navigate to URLs, fill forms, click buttons and download files.
- Anthropic reported that its safeguards cut a measured attack success rate to around 1 to 2 percent in its tests, and said even 1 percent still represents meaningful risk.
- OWASP describes excessive agency as damaging actions caused by too much functionality, permission or autonomy.
- OWASP's example is a mail-summarising assistant with a plugin that can send messages, which an injected email could use to forward private data.
- The UK NCSC says prompt injection may never be totally mitigated, so limiting what an agent can do matters more than hoping it cannot be fooled.
What a browser agent does
An AI browser agent works inside a web browser as you would: it opens pages, reads them, types into forms and clicks buttons. People use these tools to compare prices, fill in repetitive forms or gather research. The convenience comes from the same ability that creates the risk, because the agent acts with your browser’s access.
Anthropic’s research on browser prompt injection puts it plainly: every web page an agent visits is a potential vector for attack. It lists the actions that widen the risk, including navigating to URLs, filling forms, clicking buttons and downloading files.
How a page can give the agent orders
A human reads a page’s visible text. An agent reads everything, including text hidden in white-on-white fonts, tiny print, comments or metadata. OWASP’s prompt injection entry describes indirect injection: an LLM accepts input from an external source such as a website or file, and hidden instructions inside change its behaviour. One OWASP example has a summarised web page that manipulates the model into inserting an image linked to a URL, leaking the private conversation.
For an agent the consequences can be larger than a bad summary. The attacker’s goal might be to make it open a different site, submit a form, reveal text from another tab or send a message. Whether that works depends on what the agent can reach, which is why the access it has matters so much. Our prompt injection explainer walks through the mechanics.
How much do defences help?
Anthropic describes three layers for its browser agent: training with simulated malicious web content, classifiers that scan untrusted content for injections, and red teaming. It published attack success rates from an internal adaptive attacker that made 100 attempts per environment. With its improved safeguards, the rates it reported for the models tested ranged from 1.4 percent to 2.4 percent, down from between 7.6 and 11.1 percent with earlier safeguards. Those are the company’s own measurements, not independent ones.
Anthropic itself adds the key caveat: a 1 percent attack success rate, while a significant improvement, still represents meaningful risk, and no browser agent is immune. The UK NCSC reaches a similar conclusion from the defender’s side, saying prompt injection attacks may never be totally mitigated and that the realistic aim is to reduce likelihood and impact. It also advises being sceptical of any product claiming to stop prompt injection outright.
The fix is to limit the blast radius
OWASP’s excessive agency entry gives a framework you can use as a customer. It names three root causes: excessive functionality, excessive permissions and excessive autonomy. Its mail example is useful. An assistant meant only to summarise email is given a plugin that can also send messages, and an injected email makes it forward sensitive data. Nothing was broken in the model. The tool simply had more power than the task needed.
Apply that to your agent. If it only needs to research, it does not need to be signed in to your bank. If it needs to draft, it does not need permission to send. OWASP recommends requiring human approval for high-impact actions and limiting permissions to what the task needs. The NCSC puts the same idea as a rule of thumb: when an AI processes information from a party, its privileges should drop to that of the party.
Practical habits
Use a dedicated browser profile for the agent, with no saved passwords and no sensitive logins. Keep confirmations on for anything that spends money, sends a message, changes a setting or downloads a file. Do not point it at content from strangers. Scammers already build fake pages to fool people, and the same pages can be built to fool software. Our guide to AI agent permissions and risks and the note on MCP and AI tool connections cover related controls. If an agent takes an action you did not intend, stop it, review the account’s activity, change passwords and follow the data breach checklist.
What you can do
- 01Start with low-stakes tasks such as research, and keep the agent away from banking, email and work accounts until you trust the setup.
- 02Use a separate browser profile for the agent, signed out of sensitive accounts, so a hijacked session cannot reach them.
- 03Turn on and keep confirmation prompts for purchases, sending messages, changing settings and downloads.
- 04Watch the agent while it works on any page that handles money, passwords or personal data, and stop it if it does something you did not ask for.
- 05Avoid letting the agent act on content from unknown emails, forums or comment sections.
- 06Review your account activity afterwards, and revoke the agent's access if anything looks wrong.
Related reading: AI voice clone scams and the data breach tracker.
Frequently asked questions
What is an AI browser agent?
It is an AI assistant that operates a web browser on your behalf. Anthropic describes browser agents as able to navigate to URLs, fill forms, click buttons and download files, which makes them useful and also gives an attacker more to work with.
How can a web page attack an AI agent?
Through indirect prompt injection. OWASP explains that when a model reads outside content such as a website, hidden instructions in it can change the model's behaviour. A page can carry text a human never sees but the agent reads.
Has the problem been solved?
No. Anthropic says no browser agent is immune and that a 1 percent attack success rate still represents meaningful risk. The NCSC says prompt injection may never be totally mitigated.
Is it safe to let an agent buy things?
Treat it as high risk. OWASP recommends human approval for high-impact actions. Keep payment confirmation on, and complete the purchase yourself on a page you checked.
Sources
- Mitigating the risk of prompt injections in browser use, Anthropic
- LLM06:2025 Excessive Agency, OWASP GenAI Security Project
- LLM01:2025 Prompt Injection, OWASP GenAI Security Project
- Prompt injection is not SQL injection (it may be worse), UK National Cyber Security Centre (NCSC), 2025-12-08
This article reflects public information as of 2026-11-06. AI tools and rules change quickly; we update articles when new facts are published. Spot an error? See our editorial and corrections policy.