First reported forkast.news
Analysis · latest
First reported beam.ai
When AI Agent Memory Becomes a Liability
An analysis piece from beam.ai argues that persistent memory in AI agents is a design liability, cataloging four failure modes: error compounding, context degradation, security exposure via memory poisoning, and compliance risk. The article notes that a maliciously poisoned memory entry planted once can fire weeks later across users, expanding the blast radius from a single request to an agent's entire workflow history, and cites controlled-benchmark research on how irrelevant context degrades LLM reasoning. Details →First reported · updated · 5 reports nhimg.org
AI Agent Memory Poisoning: Persistent Agent Attacks
An explainer on agent memory poisoning describes how a single adversarial write into an LLM agent's persistent memory store is retrieved and executed across future sessions, unlike a prompt injection that dies when the turn ends. It draws on red-team research (AgentPoison, which backdoors memory/RAG knowledge bases, and MINJA, which injects malicious records via query-only interaction) and recommends architectural defenses: authorising writes outside the model, provenance stamping, trust-weighted retrieval, and quarantining new writes. Details →First reported · updated · 3 reports youtube.com
CyberTalks: Data Poisoning Attacks on ML & Agentic AI Systems | Jason Ross |COASP - YouTube
An explainer on AI data poisoning describes how attackers corrupt the data a model learns from, fine-tunes on, or retrieves — including training data, alignment data, and RAG knowledge bases — so a poisoned model behaves as the attacker intends while passing ordinary validation. It distinguishes data poisoning from prompt injection, jailbreaking, evasion, and model poisoning, and notes research (e.g. Carlini et al.'s web-scale poisoning work) showing under 1% poisoned data can measurably change behavior, recommending provenance, access control, monitoring, and rollback as layered defenses. Details →First reported aws.com
Memory Poisoning Attack in AI Agents - Attack vectors and defenses on AWS | AWS Builder Center
An AWS Builder Center article titled "Memory Poisoning Attack in AI Agents" discusses attack vectors and defenses for memory poisoning against AI agents on AWS. The retrievable page body contains only cookie-consent boilerplate, so the substantive technical content could not be analyzed. 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