First reported · updated · 4 reports openai.com
Lead dispatch
First reported · updated · 2 reports island.io
AgentBaiting: How Fake AI Skills Deliver Malware at Scale
The FakeGit campaign, detailed by Island security researcher Oleg Zaytsev, uses roughly 7,600 malicious GitHub repositories—over 800 posing as AI Skills or MCP servers—to deliver SmartLoader malware, which establishes persistence and installs the StealC information stealer. Researchers coined the technique 'AgentBaiting,' where AI agents like Claude Code, Gemini, and ChatGPT autonomously discover the attacker repositories, treat the malicious READMEs as legitimate documentation, and hand installation instructions to users; the operation recorded over 14 million downloads and peaked in April 2026.supply-chain · tool-abuse · malware-distribution · agent-baiting
mcp · ai-agents · llm · github
Severity
0.78
The wire · latest
First reported github.com
AI Agents Project Viewer Privilege Escalation via run_node_tool · Advisory · n8n-io/n8n
A GitHub Security Advisory (GHSA-x5vx-c2c8-m3w9) for n8n discloses a privilege-escalation flaw in its AI Agents feature: a read-only Project Viewer could chat with an agent whose node tools were enabled and, via the run_node_tool authorized only by the agent:execute scope, execute arbitrary tool nodes using the project's credentials without authorization checks. Where command- or file-capable nodes (Execute Command, SSH) are enabled, this could extend to arbitrary command execution on the n8n host. The issue is fixed in n8n versions 2.29.8 and 2.30.1. Details →First reported traefik.io
MCP Gateway Best Practices | Traefik Hub Documentation
Traefik Hub documentation outlines security best practices for deploying an MCP Gateway in production, covering On-Behalf-Of (OBO) token delegation per RFC 8693, Task-Based Access Control (TBAC) for AI agents, and a defense-in-depth 'Triple Gate' pattern. The guidance emphasizes least-privilege access so that a compromised MCP server does not grant an attacker access to all backend resources. Details →First reported airia.com
AI Agent Permission Sprawl: How Agents Accumulate Excessive Access Over Time
An Airia blog post analyzes how AI agents accumulate excessive permissions over time — being repurposed without permission review, lacking audit triggers, provisioned by developers rather than IAM teams, and deployed as ungoverned shadow agents. The post also warns of privilege escalation via delegation chains in multi-agent architectures where a sub-agent inherits an orchestrating agent's broad access. Details →First reported · updated · 2 reports cloudsecurityalliance.org
MCP Security in the Cloud: Where the Real Risks Begin
A Darktrace/CSA analysis (drawing on the arXiv paper 'Securing the Model Context Protocol (MCP): Risks, Controls, and Governance') outlines seven MCP security risks CISOs should prepare for, including content-injection/prompt-injection attacks, over-privileged agents, tool poisoning, supply-chain compromise via malicious MCP servers, and data exfiltration. It notes MCP handles only connection mechanics without built-in identity or access controls, amplifying the 'lethal trifecta' of sensitive-data access, untrusted content exposure, and external communication. Details →First reported arxiv.org
A Security Analysis of the OpenClaw AI Agent Framework
Researchers detailed three now-patched high-severity flaws (GHSA-hjr6-g723-hmfm, GHSA-9969-8g9h-rxwm, GHSA-575v-8hfq-m3mc; CVE-2026-46817, CVE-2026-55200) in the OpenClaw personal AI assistant framework that compose into a complete unauthenticated remote code execution path — from an LLM tool call triggered via a WhatsApp message to command execution on the host. The chain abuses OS command injection and an incomplete disallowed-input filter in the exec allowlist, whose closed-world lexical parsing is defeated by shell line continuation, busybox multiplexing, and GNU option abbreviation; a companion arXiv analysis taxonomizes 470 advisories and shows a malicious plugin skill bypassing the exec pipeline entirely. Details →First reported bleepingcomputer.com
Agentic AI Has an Identity Problem and Attackers Know It
A vendor (Token Security) commentary arguing that AI agents act as privileged identities accessing data and triggering workflows across enterprise systems, and that governing these non-human identities is becoming essential. The piece frames identity governance as an emerging security gap attackers can exploit. Details →First reported adversa.ai
OWASP ASI03: Identity & Privilege Abuse in AI Agents
A technical guide on OWASP's ASI03 (Identity & Privilege Abuse in AI Agents), covering five identity abuse vectors, the Salesloft Drift breach case study, the attack lifecycle, and detection/prevention with task-scoped, time-bound access. 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