Attributed metadata history
Up to 100 retained publisher events per page for 84804ea62748808cc60cf2840a804d7b7f53f9bac3b239c1fa6649c018ba33ea. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_c25d91fa3ad9ae9ac7
observed · 2026-10-12 14:53:04 UTC
Grok is the chatbot of xAI. It’s a state-of-the-art model, chatbot and recently also API. It has a Web UI and is integrated into the X (former Twitter) app, and recently it’s also accessible via an API. Since this post is a bit longer, I’m adding an index for convenience: Table of Contents High Level Overview Analyzing Grok’s System Prompt Prompt Injection from Other User’s Posts Prompt Injection from Images Prompt Injection from PDFs Conditional Prompt Injection and Targeted Disinformation Data Exfiltration - End-to-End Demonstration Rendering of Clickable Hyperlinks to Phishing Sites ASCII Smuggling - Crafting Invisible Text and Decoding Hidden Secrets Hidden Prompt Injection Creation of Invisible Text Grok API is also Vulnerable to ASCII Smuggling Developer Guidance for Grok API Automatic Tool Invocation Responsible Disclosure Conclusion High Level Overview Over the last year I have used Grok quite a bit. It’s pretty good and I use it daily, especially the recent image creation capabilities are impressive, but I hadn’t really looked at it from a security perspective. So, I decided to assess the overall security posture with some of
Fingerprint: 5eff1347043752aa7751332b70354cf7e4991eafe88966eb49443ea05ed048cb
intelligence_src_c25d91fa3ad9ae9ac7
observed · 2026-10-12 14:53:03 UTC
available
Fingerprint: 0a2f1bebc7ea800736eafab237a0ddecfb8797a02d23951e8aa80935e2f3446f