Skip to content

Agentic AI Browsers Are a New Attack Surface: What Businesses Should Know Before Employees Start Using Them

October 13, 2026/5 min read/DataTap team
Illustration of a web browser window with an AI agent icon surrounded by warning shield symbols, representing agentic AI browser security risk

What Is an Agentic AI Browser, and Why Does It Matter for Your Business?

An agentic AI browser is a web browser with a built-in AI agent that can click, fill out forms, read your inbox, and complete multi-step tasks on your behalf — not just summarize a page. Examples include ChatGPT Atlas, Perplexity Comet, Claude in Chrome, Gemini in Chrome, and Microsoft Copilot in Edge. Because these agents act with the user’s own logins and permissions, a single malicious instruction hidden in a webpage, email, or calendar invite can turn that convenience into a liability.

For a business, that liability looks exactly like every other cybersecurity risk you already manage: compromised credentials, stolen customer data, and unauthorized financial transactions — except the attacker never needs the employee to click anything.

The PleaseFix Vulnerability Class: Zero-Click Hijacking Across Major AI Browsers

In August 2026, security research firm Zenity Labs published findings on a vulnerability family it calls PleaseFix, which affects agentic browsers including Claude in Chrome, Gemini in Chrome, Perplexity Comet, ChatGPT Atlas, and Copilot Edge. The attacks use a technique Zenity named "Intent Collision": hidden instructions buried in ordinary content — an email, a calendar invite, a social media post — redirect the agent to act on an attacker’s behalf, using the victim’s own accounts and permissions.

The real-world examples Zenity demonstrated are worth sitting with:

  • A poisoned calendar invite in Perplexity Comet triggered unauthorized file access, credential theft, and a full 1Password account takeover — with no clicks from the user.
  • An ordinary-looking link under a social media post hijacked ChatGPT Atlas into sending phishing messages through the victim’s WhatsApp and placing fraudulent Amazon purchases on their credit card.
  • A malicious email request manipulated Claude in Chrome into exfiltrating Gmail data, sharing Google Drive files, and taking over the user’s Slack, X, and Claude accounts.

This isn’t a hypothetical. It’s a working exploit chain Zenity presented at Black Hat USA 2026, built entirely around content an employee would encounter during a normal workday.

Independent Research Confirms the Problem Runs Deeper Than One Vendor

Zenity’s findings aren’t an isolated claim. A University of Washington research team separately tested seven popular agentic browsers and found that four of them — ChatGPT Atlas, Chrome with Gemini, Claude for Chrome, and Perplexity Comet — created conditions where a malicious website could bypass the browser’s same-origin policy, the three-decade-old rule that keeps one website from reading data on another according to the university’s announcement. Researchers ran a working proof-of-concept attack against Atlas in which a malicious site stole information from another site the agent had open — comparable to an ad on an email provider’s page reaching into the user’s inbox.

The same study found Microsoft Edge with Copilot, Brave Leo, and Firefox’s limited AI mode held up better, because their agents operate with more restricted permissions. That distinction matters: not every "AI browser" carries identical risk, and the safer designs tend to be the ones that ask for explicit confirmation before taking consequential actions.

Even the Vendors Admit This May Never Be Fully Fixed

Perhaps the most telling detail is OpenAI’s own assessment. In a December 2025 blog post on hardening Atlas, OpenAI acknowledged that "prompt injection, much like scams and social engineering on the web, is unlikely to ever be fully ‘solved.’" The company described building an automated, reinforcement-learning-trained "attacker" to continuously probe Atlas for new exploits — a discover-and-patch cycle, not a permanent fix. OpenAI’s own example of a successful attack involved a malicious email instructing the agent to send a resignation letter to the user’s CEO when the employee simply asked it to draft an out-of-office reply.

In other words, the company building one of the most widely used agentic browsers is telling customers this is an ongoing arms race, not a solved problem.

What This Means for Your Team Right Now

If employees at your business have installed ChatGPT Atlas, Perplexity Comet, or similar tools — or enabled "agent mode" inside an existing browser — treat it the same way you’d treat any new piece of software with access to email, files, and payment methods. A few practical steps:

  • **Keep agent mode off high-value accounts.** Don’t let an AI browser agent log into password managers, banking portals, or accounting software unattended.
  • **Require confirmation for consequential actions.** Sending messages, making purchases, or sharing files should prompt a manual approval step, not run automatically.
  • **Audit what’s already installed.** Shadow AI adoption — tools employees added without IT’s knowledge — is exactly how this risk enters a business unnoticed, a pattern we’ve covered before.
  • **Limit which browser is standard-issue.** If your team needs AI browsing assistance, the UW research suggests Edge with Copilot or Brave Leo currently carry less structural risk than Atlas or Comet.

This risk sits alongside two issues we’ve written about recently: MCP connections that give AI agents direct access to business data, and the Microsoft 365 Copilot SearchLeak flaw. The common thread is that AI tools inherit the access level of the person using them — which means your existing identity and access controls are doing more security work than ever before.

The Bottom Line

Agentic AI browsers aren’t a future threat to plan around — they’re already installed on some of your employees’ machines today, and independent researchers at Zenity Labs and the University of Washington, along with OpenAI itself, agree the underlying prompt injection problem doesn’t have a clean fix yet. Treating these tools with the same access controls, approval workflows, and audit visibility you’d apply to any system touching customer data and company funds is the most realistic path forward until the vendors close more of the gap.

If you’re not sure what’s already running inside your network — AI browsers included — a managed IT partner can help you find out before an attacker does.

Sources

All articles