Agent incident database
Perplexity Comet: a Reddit comment hijacked the browser agent
20 Aug 2025Perplexity · Comet browsercredential exposuredisclosed vulnerability
Brave showed that hidden text in a Reddit comment could take over Perplexity's AI browser when a user asked it to summarise the page. The agent fetched the user's email address and a login code from Gmail and posted them publicly for the attacker.
How it unfolded
Each step on its own looked like ordinary agent work. The harm came from the sequence.
- 1
Read a Reddit page containing a hidden comment written by an attacker
- 2
Model treated the hidden text as instructions from the user
- 3
Opened the user's Perplexity account settings and read their email address
- 4
Opened the user's logged-in Gmail and read a one-time login code
- 5
Posted the email address and code as a public reply on Reddit
harm
Which policy would have stopped this?
In our reading of the reports, these policies from the open library stop the harmful step before it runs.
- External content taint: high-impact actions require a fresh gate: The agent read a page with hidden instructions, then took high-impact steps in the user's accounts. After external content, those steps need a fresh approval.
Open External content taint: high-impact actions require a fresh gate in the playground and build the path yourself.
This is our reading of public reporting. We haven't run it against the original systems.
What happened
Brave reported the issue to Perplexity on 25 July 2025 and published it on 20 August 2025. In the proof of concept, instructions were hidden behind a spoiler tag in a Reddit comment. When the user clicked Comet's 'Summarize the current webpage', the agent treated the hidden text as user requests. It opened the user's Perplexity account page to get their email address, requested a one-time password via a lookalike domain, opened the user's already-logged-in Gmail to read the code, and replied to the Reddit comment with both. With that, the attacker could take over the victim's Perplexity account.
Outcome
Perplexity shipped an initial fix on 27 July 2025, which Brave found incomplete; testing on 13 August suggested a patch. In an update on publication day, Brave said the attack type was still not fully mitigated and re-reported it. Perplexity did not comment to The Register.
Sources
- Agentic Browser Security: Indirect Prompt Injection in Perplexity Comet, Brave, 2025-08-20
- Perplexity's Comet browser faced prompt injection vuln, The Register, 2025-08-20
A summary of public reporting. The step-by-step timeline is our reading of those sources; where they differ, we say so above.
Your agents
Could this happen to yours?
For developers
Build a path yourself
Recreate a sequence in the playground and see how policies treat it.