Claude Chrome Extension Flaw Enabled Zero-Click Prompt Injection via Trusted Subdomain XSS
Researchers disclosed a critical zero-click vulnerability chain in Anthropic’s Claude Chrome extension that allowed a malicious website to inject prompts into the AI assistant without any user interaction. The attack relied on the extension trusting any *.claude.ai origin and a DOM-based XSS flaw in an older Arkose Labs CAPTCHA component hosted on a-cdn.claude.ai; by loading the vulnerable component in a hidden iframe and sending a crafted postMessage, attacker-controlled JavaScript could appear to come from a trusted Claude origin and submit prompts as the victim.
Successful exploitation could have exposed more than 3 million users to account and data compromise, including theft of Gmail OAuth tokens, access to Gmail, Google Drive, and Claude chat history, and invisible actions such as sending emails on the user’s behalf. KOI Security researcher Oren Yomtov reported the issue to Anthropic in late December 2025, Anthropic patched the extension by tightening origin validation to https://claude.ai in January 2026, and Arkose Labs separately fixed the XSS issue in February 2026 after the vulnerable resource was disabled.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
5 events from the most recent confirmed update back to the earliest known activity.
Researchers publicly disclose zero-click Claude extension exploit chain
Researchers publicly revealed that the chained flaws could have allowed silent prompt injection against Claude Chrome extension users, potentially exposing conversation history, Gmail and Drive data, OAuth tokens, and enabling actions such as sending emails on a victim's behalf. Reports said the issue affected a user base of more than 3 million before the fixes were applied.
Arkose Labs fixes CAPTCHA XSS on a-cdn.claude.ai
Arkose Labs patched the vulnerable CAPTCHA component, and the previously exploitable URL later returned HTTP 403. This remediation closed the XSS portion of the exploit chain used against the Claude extension.
Arkose Labs XSS flaw is separately reported
The DOM-based XSS vulnerability in the Arkose Labs CAPTCHA component hosted on a-cdn.claude.ai was separately disclosed to Arkose Labs. This second flaw was necessary for the full exploit chain because it enabled attacker-controlled JavaScript execution from a trusted Claude subdomain.
Anthropic patches Claude Chrome extension origin validation
Anthropic fixed the extension-side issue by tightening trusted origin checks from any claude.ai subdomain to exactly https://claude.ai. This patch blocked malicious websites from abusing the extension's overly broad allowlist to send trusted messages without user interaction.
KOI Security reports Claude extension vulnerability chain to Anthropic
KOI Security researcher Oren Yomtov responsibly disclosed a zero-click prompt-injection vulnerability chain affecting Anthropic's Claude Chrome extension. The issue combined an overly broad *.claude.ai trusted-origin allowlist with a DOM-based XSS flaw in an Arkose Labs CAPTCHA component hosted on a-cdn.claude.ai.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
3 references tracked. Mallory keeps watching after this page renders.
ShadowPrompt: Zero-Click Prompt Injection Chain in Anthropic’s Claude Chrome Extension
socradar.io
Open sourceClaude Chrome Extension 0-Click Vulnerability Enables Silent Prompt Injection Attacks - Cyber Security News
cybersecuritynews.com
Open sourceClaude Extension Flaw Enabled Zero-Click XSS Prompt Injection via Any Website
thehackernews.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


