First reported · updated · 4 reports hiflylabs.com
Lead dispatch
First reported · updated · 3 reports embracethered.com
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
Severity
0.85
The wire · latest
First reported pipelab.org
Denial of Wallet
PipeLab's explainer defines "denial of wallet" as a cost-abuse attack against metered AI-agent systems, where a hijacked, prompt-injected, or looping agent repeatedly calls paid surfaces (model tokens, tool calls, MCP servers, SaaS APIs) until the bill or quota is exhausted. The page argues that per-session budget caps fail because agents can reset the session lifecycle to mint fresh allowances, and pitches Pipelock v3.3, which keys budgets to a derived identity subject rather than an MCP session id. Details →First reported cyberdefensemagazine.com
The Zero Trust Architecture For AI Agents On Google Cloud
An article by a Google author on Cyber Defense Magazine outlines a Zero Trust architecture for securing AI agent workloads on Google Cloud, describing the agentic threat landscape (prompt injection, insecure tool use/excessive agency, RAG data exfiltration and poisoning, denial-of-wallet) and defensive pillars such as credentialless Workload Identity, IAM Conditions, and Cloud Armor edge defenses against prompt injection. Details →First reported bitsight.com
Token Torching: How AI Cost Attacks Threaten Your Business
Bitsight's Emma Stevens explains "token torching," a Denial-of-Wallet (DoW) attack in which an adversary crafts prompts or workflows that force an LLM system to burn through excessive tokens, compute time, and money. The piece maps the risk to OWASP's LLM10:2025 Unbounded Consumption category, noting impacts such as denial of service, economic loss, and service degradation. Details →First reported paloaltonetworks.com
Potential denial of wallet abusing AI services • Cortex XSIAM Analytics Alert Reference by data source • Palo Alto Networks documentation portal
A Palo Alto Networks Cortex XSIAM analytics alert reference page documents a detection named 'Potential denial of wallet abusing AI services,' which flags abuse of cloud AI services (via AWS Audit Log data) to drive up costs in a denial-of-wallet style attack. The page is a product documentation entry describing the built-in detection rather than a technical write-up of the attack mechanism. Details →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.
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.
- GET /feed.xml — RSS 2.0, every item
- GET /api/items — read-only
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