Researchers say xAI’s Grok web chat can be manipulated by a poisoned web page so the AI follows hidden attacker instructions. The twist is the instructions are strongly encrypted, so safety scanners don’t recognize them, yet Grok can decrypt and act on them, including leaking a user’s chat details by sending them out in a URL.
Key findings
- Grok is described as vulnerable to indirect prompt injection delivered via a malicious (poisoned) web page.
- Attackers can hide the malicious instructions using strong encryption so guardrail scanners cannot inspect the true content.
- The AI can be induced to decrypt the instructions inside its code execution environment and then follow them.
- A proof-of-concept shows exfiltration of Grok chat history and user metadata by appending data to a URL as parameters.
- Gemini was reportedly not vulnerable to the same data-exfiltration flow due to restrictions, but the technique was used to bypass safety filters to produce prohibited content.
Who’s being targeted
- Commonly targeted roles: Executives, All employees using AI assistants/agents, IT and Security leadership, Data privacy/compliance teams.
- Affected industries: AI and ML platforms, Technology, Any organization whose staff use AI web chat/agent tools.
- Attack channels: website.
- Impersonated: A benign web page/content source (the page itself is the lure), A web page the user asks Grok to summarize (attacker-controlled).
Awareness takeaways
- Treat ‘summarize this webpage’ requests as risky when the page is untrusted, AI agents can be tricked into following hidden instructions, not just summarizing.
- Be alert for AI outputs or workflows that involve decrypting/decoding content or running code, this can be used to bypass safety controls.
- Assume AI chat history may be exposed if the agent is tricked into ‘sending’ data out (for example, embedding it into URLs). Avoid putting sensitive information into AI chats unless approved and protected.
- Even when providers have guardrails, attackers may bypass them by moving harmful logic into the AI’s execution environment (tools/runtime).
Red flags to watch for
- Content includes instructions to decrypt/execute code rather than just summarize
- Unexpected requests for the AI to access conversation history or account details
- The AI attempts to send data out via links/URLs
- AI tries to open or construct URLs containing personal or conversation data
- AI behavior shifts from summarizing to ‘sending’ or ‘transmitting’ information
- The page includes encrypted blobs plus a key and instructions to decrypt
Read the video transcript
You paste a link into Grok and hit “summarize this page”… and that page quietly steals your chat history. Researchers showed a poisoned web page that Grok reads. Hidden on the page is encrypted text plus a key. Grok decrypts it inside its tools and follows the secret instructions instead of just summarizing. In the demo, Grok was tricked into grabbing the user’s name, location, subscription tier, and full chat history, then stuffing it into a long URL as parameters, ready to be sent out. Aha moment: that innocent “summarize this page” can leak everything you told Grok. Your move: only use Grok’s browsing or summarize features on trusted sites you’d be comfortable sending your whole chat history to.