- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper proposes Zombie, which extends memory poisoning in LLM agents by getting agents to repeatedly refresh malicious instructions picked up from webpages. This can keep the instructions active across sessions and trigger unauthorized actions during later tasks.
Critical strengths
• Under a realistic threat model. The attacker controls external content without direct access to the agent’s memory, model parameters, or tools, which is more common in real environment.
• Poisoned behavior persistence. The paper measures repeated unauthorized actions during later benign tasks, focusing on the long-time control instead of traditional prompt injection.
Critical weaknesses
• Limited novelty or contribution over existing memory poisoning. The self-evolving setting in consists of memory updates while the model, workflow, and tools remain fixed. There are works already evaluate persistence under multiple update policies. The paper should compare the differences with such works, rather than present memory evolution or persistence alone as a new security problem.
Questions for authors
• Limited coverage of memory update mechanisms. Figure 4 compares raw history, reflection, and experience refinement, but the ASR drops sharply under the latter two conditions instead of showing generalization. The authors should compare more memory update policies and try to improve the effectiveness rather than only effective in the simplest raw history.
• User-side utility-preservation is not established. Table 4 reports substantial utility losses, including a drop from 76.5% to 47.6% for DeepSeek. Thus, I think it is easier to be noticed by the user with the low utility performance.
• What’s the persistant performance without renewed exposure. The paper describes a loop that revisits attacker-controlled content and writes it back into memory. The paper does not measure how long the stored injection remains effective after the attack source becomes unavailable or returns clean content. I think it heavily relies continued access to that source.