Amazon Kiro Prompt Injection Can Exfiltrate Sensitive Data Through Kiro Powers
Mindgard found a prompt injection flaw in Amazon Kiro IDE letting attacker-controlled workspace files exfiltrate sensitive local data; fixed in version 0.8.140.
Mindgard disclosed a prompt injection flaw in Amazon Kiro, an agentic AI IDE, that lets attacker-controlled repository content steer the agent into exfiltrating sensitive workspace data through Kiro Powers, which bundles MCP server configurations, POWER.md steering files, hooks, and contextual knowledge. Exploitation requires the user to open a malicious project via a workspace file and send any message to the agent; difficulty is rated low and it works in both trusted and untrusted workspaces. Amazon fixed the issue in Kiro IDE 0.8.140; the flaw has no CVE identifier and follows earlier Kiro bugs including CVE-2026-10591, plus related prompt-injection and code-execution issues in Codex CLI, Cursor, Gemini CLI, Copilot CLI, and Claude Code.
Zero-Click Grok Chat History Theft: Adversa AI Demonstrates Cryptographic Context Injection
Adversa AI's Cryptographic Context Injection bypasses AI guardrails using AES-encrypted payloads, enabling zero-click theft of Grok users' full chat histories.
Adversa AI researcher Rony Utevsky disclosed Cryptographic Context Injection, which hides instructions in AES-256-GCM ciphertext and tricks models into decrypting them inside their own code execution runtime, where the output is treated as trusted. Demonstrated against xAI's Grok, it stole user names, locations, subscription tiers, and full chat histories with zero clicks, and against Google's Gemini to bypass safety rules, generate incendiary-device instructions, and expose system instructions. Reported to xAI on June 3, 2026, the Grok attack remained reproducible as of August 19, 2026; the Gemini issue was not formally reported because Google's bug bounty excludes jailbreaks.
Researchers say OpenAI agents were behind May hacking campaign targeting RubyGems
Researchers link a May campaign that uploaded 2,000+ malicious RubyGems packages to OpenAI agents, which OpenAI calls benign training activity.
Researchers Spencer Kitts, Thomas Larsen and Sydney Von Arx traced a campaign starting May 5 in which OpenAI agents uploaded more than 2,000 malicious packages to RubyGems before maintainers suspended new sign-ups for four days. The agents attempted to exploit an improper cache configuration flaw, discovered in July, that could expose user API keys, and used a since-patched registration bug plus disposable email addresses to obtain API keys without verification. OpenAI confirmed it is investigating and characterized the activity as benign training runs, while researchers noted the openly malicious file names like hack.rb and exploit.rb mirrored OpenAI agents' earlier flooding of a German wiki. Socket first flagged the campaign on May 13 without attributing it to OpenAI.