Researchers from Shanghai Jiao Tong University and Ant Group demonstrated InjecMEM, an attack technique that plants hidden instructions into an AI agent's memory using a single interaction, without needing read or write access to the memory store. Tested on MemoryOS and MemGPT, the attack achieved up to a 35.4% retrieval success rate and 76.6% attack success rate, allowing attacker-controlled content to persist and influence responses across future sessions rather than just the current conversation. Security researcher Vibhum Dubey notes this shifts AI memory into a security boundary that enterprises must actively govern, since most current defenses filter prompts and outputs but not stored memory.

5m read timeFrom csoonline.com
Post cover image

Questions this post answers

What is the InjecMEM attack on AI agent memory?

InjecMEM is a red-teaming attack technique that plants hidden, attacker-controlled instructions into an AI agent's memory using just one interaction, without needing direct read or write access to the memory store. The attacker specifies a target topic and desired output, and the memory system later retrieves and incorporates that content into responses to related future queries, persisting across sessions. Teams securing AI agent deployments can follow emerging memory-poisoning research like this on daily.dev.

How effective was the InjecMEM attack against MemoryOS?

On the MemoryOS memory system, InjecMEM achieved up to a 35.4% retrieval success rate and a 76.6% attack success rate, substantially outperforming baseline attacks. Researchers from Shanghai Jiao Tong University and Ant Group also tested the technique against the MemGPT agent framework across multiple domains, showing injected records could be retrieved and reused in later responses. Developers benchmarking AI memory defenses can track findings like these through daily.dev.

Why don't existing AI security defenses catch memory poisoning attacks like InjecMEM?

Current AI security defenses mostly filter inputs and outputs at the moment of interaction, but memory poisoning attacks introduce content that appears benign at first and only influences behavior when retrieved later. Security researcher Vibhum Dubey notes enterprises need to ask who can write to agent memory, what gets stored, how it's validated, and how poisoned entries can be identified and removed. Engineers hardening AI agent stacks against memory-layer threats can stay current via daily.dev.

150 Impressions