Skip to content
CYCRAFT
SECURING SESSION
CyCraft
Back to Blog
Web Security05 Nov 2025

The Invisible Hack Indirect Prompt Injection Targets AI Browsers

Security researchers at Brave revealed a critical weakness in AI-powered browsers: attackers can hide instructions in web content (white-on-white text, HTML comments, spoilers, screenshots) that an assistant will obediently execute. When the assistant runs with your signed-in privileges, a single click can hand an attacker emails, one-time passwords, and full account access.

By EthicalByte4 min read

What’s Happening?

Attackers embed hidden prompts in page content invisible text, comments, spoiler tags, or nearly-invisible overlays. AI assistants (like Comet in the Brave demo) can't reliably separate user intent from page content, so they execute both. The result: data exfiltration using the user's own authenticated sessions.

How the Exploit Worked (Demo)

  • Hidden payload in a Reddit spoiler triggered by “Summarize this comment”.
  • Assistant logged into Perplexity to record the user email.
  • Assistant opened Gmail (user already authenticated) and grabbed an OTP.
  • Assistant posted email + OTP back to the attacker’s comment full account takeover with one click.

No phishing link. No classic malware. Just a trust boundary collapse between page content and assistant commands.

Why This Is Terrifying

AI browsers often act with the same session privileges as you. If you’re logged into email, bank, or work apps, the assistant’s actions inherit those privileges meaning hidden instructions can access sensitive assets without human consent.

Some browsers auto-send page content to the AI engine (background summarization). That behavior removes even the “click” requirement visiting a malicious page might be enough.

Attack Surface & Tech Notes

  • Hidden text layers and HTML comments are simple carriers for malicious prompts.
  • Screenshots with near-invisible text (steganographic overlays) can embed instructions.
  • Auto-ingestion (background fetch model prompt) drastically widens the attack surface.
  • Mitigations require both UI/UX isolation and server-side policy enforcement from browser vendors.

Immediate Mitigations (For Users & Admins)

  • Disable AI summarization or assistant features while logged into sensitive accounts.
  • Use separate browser profiles for sensitive work (no third-party AI features in that profile).
  • Turn off auto-send/background content processing for AI features.
  • Enforce strict CSPs and sanitize third-party content in corporate web apps.
  • Monitor for unusual token reuse, rapid OTP requests, and anomalous API calls.
AI BrowserPrompt InjectionBraveCometSecurityBrowser Threats

Interactions

18

Comments (0)

Anonymous