- Rating
- 2(+1)
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2(+1)
- Soundness
- 2(+1)
Read review
Paper summary
The authors investigate a relatively interesting problem: memory attacks that are not injected all at once, but instead are broken into fragments and assembled through the memory management cycle. They propose a three-stage attack pipeline, starting from behavioral fingerprinting, then compositional fragment construction, and finally adaptive fragment evolution. Empirically, the paper reports an average ASR of 87.55, much higher than the chosen baselines, along with ablations that help show the robustness of the attack.
Critical strengths
- The paper provides a comprehensive experiments across different memory backends, task domains, and baselines, along with ablations on the main stages of the attack.
Critical weaknesses
- The paper is not well written. The main method, including the behavioral fingerprinting, fragment construction, and fragment evolution stages, remains too abstract even after I read the appendix. This is a critical weakness for a paper whose main contribution is methodological. In particular, it is still not clear to me how the fragments are actually submitted as ordinary interactions, or how the adaptive revision loop works in practice given how dataset-specific the setup appears to be. I had to rely heavily on the appendix to piece together the procedure, and even then some parts still feel under-specified. This significantly hurt my ability to understand and evaluate the paper.
- The novelty also feels narrower than what the authors claim. While the paper emphasizes risks in evolving memory systems, the overall idea still reads to me as a combination of existing directions in memory poisoning, multi-fragment injection, and iterative refinement. Even though the empirical results look strong, the clarity issues make it hard for me to tell whether there is a deeper novelty here beyond packaging these existing ideas together in one framework.
Questions for authors
- Can the authors provide one concrete running/end-to-end attack example, showing exactly how the behavioral fingerprinting, fragment construction, and fragment evolution stages work in practice, and how they ultimately lead to the final attack?
- Can the authors clarify what is the novelty and how is fundamentally new compared to prior research?
Reminder: Please Read and Discuss the Author Rebuttal
Dear Reviewers,
As the discussion period ends on November 18 (AoE), please take this final opportunity to review the authors’ rebuttal and discuss any remaining concerns with them. Even if the rebuttal does not change your assessment, I would appreciate it if you could briefly acknowledge that you have read and considered it.
Thank you for your time and contribution.
AC, ICLR 2027