Lead dispatch

AWS Kiro: Arbitrary Code Execution via Indirect Prompt Injection

Researchers found a vulnerability (CVE-2026-10591) in AWS Kiro, an agentic IDE, where hidden instructions planted in a web page or source file that Kiro processes can trigger indirect prompt injection to rewrite Kiro's own MCP server configuration (~/.kiro/settings/mcp.json) or allowlist arbitrary Bash commands in .vscode/settings.json, achieving arbitrary code execution on the developer's machine with no approval prompt. The human-in-the-loop approval boundary is bypassed because Kiro can write to these config files without user consent, and AWS has issued a fix and CVE.

indirect-prompt-injection · prompt-injection · remote-code-execution · tool-abuse · config-poisoning
ai-agents · mcp · llm · agentic-ide

The wire · latest

More filters

Arbitrary code execution and Claude Code CLI: How Claude executed code before you click 'trust' | Sonar

Researchers disclosed that AI coding agents including Anthropic's Claude Code, OpenAI Codex, Cursor, and goose can be tricked into executing attacker code via malicious Git configuration in an untrusted repository. Setting core.fsmonitor in a repo's .git/config causes the agent's git diff context-gathering to run arbitrary commands on the host before any trust prompt, model call, or tool approval (CVE-2026-72718 for goose, fixed in 1.44.0; Claude Code fixed in v2.0.71). The commands run with the user's privileges, enabling secret and API-key exfiltration. Details →

Amazon Kiro: AI Is Breaking Vulnerability Disclosure Processes

Mindgard disclosed a prompt-injection vulnerability in Amazon Kiro, an AI-powered agentic IDE, that lets attacker-controlled repository content coerce the Kiro agent into reading local sensitive data, modifying a workspace URL, and triggering an outbound request that exfiltrates the secret. The flaw was reproduced in Kiro IDE 0.7.45 on Windows in both trusted and untrusted workspaces via Kiro Powers (MCP configs and POWER.md steering files); exploitation requires the user open a malicious workspace file and message the agent, and is assessed as low difficulty. Details →

Unauthorized Publication of a Malicious npm Package affecting CI

Jscrambler disclosed that a threat actor used compromised npm publishing credentials to publish a malicious version of its 'jscrambler' npm package (versions 8.14, 8.16, 8.17, 8.20), which ran an infostealer during the preinstall hook and was downloaded around 1,479 times in a two-hour window. Per Socket's analysis, the malware harvested developer credentials, cloud secrets, crypto wallets, browser data, and notably AI coding tool and MCP configurations (Claude, Cursor, Windsurf, VS Code, Zed), using ChaCha20-Poly1305 obfuscation to resist analysis. Jscrambler revoked credentials and released a safe version 8.22. Details →
See the API docs to pull all 954 items →

How the wire is made

Poll & cluster

Internet is crawled for AI security news and near-duplicate coverage is embedded and grouped into durable items.

Curate

AI Agent filters for agentic-AI relevance, classifies and tags each item, scores severity for threats, and writes the summary.

Read the full methodology →

Every item here is one machine-curated intelligence object, not a headline.

Read the wire for free. There is a small charge to ask the index questions.

The wire, open

The complete curated feed, no key required.

Subscribe to the RSS feed

The vector desk

Query the index by meaning, not just keyword.

  • GET /api/items?tags=&minSeverity=&itemType=
  • GET /api/search?q= — keyword
  • GET /api/semantic?q= — vector
Preview semantic search