Research · latest

More filters

Your Agent's Memories Are Not Its Own: Forged Reasoning Attacks on LLM Agent Memory and Defenses

Researchers at Penn State introduce FARMA (Forged Amplifying Rationale Memory Attack), which poisons an LLM agent's remembered reasoning traces rather than its factual knowledge, using evasive language to bypass keyword filters and self-referential reinforcement to defeat consensus-based defenses, achieving up to 100% attack success including against A-MemGuard. They also propose SENTINEL, a layered defense whose Reasoning Guard structurally analyzes memory entries for forgery, reducing attack success to as low as 0% with no false positives across 326 benign traces. Details →

Hidden in Memory: Sleeper Memory Poisoning in LLM Agents

The arXiv paper "Hidden in Memory: Sleeper Memory Poisoning in LLM Agents" (2605.15338), explained in a companion Medium write-up, demonstrates a delayed attack in which adversarial content in a document, webpage, or repository causes a stateful LLM assistant to store a fabricated memory about the user that re-emerges across future sessions. Across tested assistants, poisoned memories were written up to 99.8% of the time on GPT-5.5 and 95% on Kimi-K2.6, and among successful retrievals they steered attacker-intended agentic actions in 60–89% of evaluations; the authors release code on GitHub. Details →

Prompt injection isn't the bug, AI agent frameworks are

Check Point researchers Yarden Porat and Shahar Tal disclosed 11 vulnerabilities across major AI agent frameworks (LangChain, LangGraph, CrewAI, AutoGen, Microsoft Agent Framework, Google ADK), arguing that the real risk is how frameworks handle prompt injection rather than injection itself. Their findings include classic flaw classes—insecure deserialization, SSRF, path traversal, use-after-free—such as a critical checkpoint deserialization bug in Microsoft Agent Framework that allowed remote code execution via poisoned agent state; Microsoft paid a $10,000 bounty and fixed it. Details →

Forensic Trajectory Signatures for Agent Memory Poisoning Detection

The paper 'Forensic Trajectory Signatures for Agent Memory Poisoning Detection' by Jun Wen Leong identifies a behavioral invariant in LLM agents under persistent memory poisoning: successful attacks require calling memory_recall_fact before email_send_email. A rule and Random Forest classifier over trajectory features achieve high AUC (up to 0.99) across 9 models, but a preregistered follow-up (N=4,360, 13 models) reveals benign memory-grounded sends produce the same signature, causing high false positives; the recall_before_send pattern is an attack precondition rather than a maliciousness predicate, requiring recipient-metadata gating to restore separation. Details →

New MCP Benchmark Highlights Server Drift Dangers

An MCP Benchmark study scanned 10,831 Model Context Protocol servers and linked poor tool-description quality ("description smells" like missing return fields, wrong parameter semantics, and duplicate tool names) to measurably higher exploitation rates, with servers rated 'poor' tripling successful-attack probability. The research characterizes 'MCP drift' — unreviewed post-deployment changes to tool descriptions, parameters, or capabilities — as a live supply-chain threat, sometimes via benign onboarding followed by malicious rewrites weeks later, and notes simple 27-line mitigations eliminated high-severity findings in lab tests. 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