'Self-State Attacks' Formalize a New Threat Class: AI Agents Poisoned via Their Own Memory Files, OS Defenses Structurally Insufficient

There is a specific kind of AI security problem that has been sitting in plain sight while everyone argued about prompt injection: what happens when the agent's own state files are the thing that gets poisoned. A [new paper on arxiv](https://arxiv.org/abs/2607.17986) by Yimeng Chen, Nathanaël Denis, Roberto Di Pietro and Jürgen Schmidhuber gives that failure mode a name, self-state attacks, and asks how far operating system defenses can actually take you against it. The setup is direct. Self-hosted AI agents read and write their own memory and configuration files to function, and the authors' claim is that an agent may get compromised via corruption of its own state, a compromise realized via legitimate OS system call invocation. They formalize the space along four axes, Target (instruction, memory, or configuration), Mechanism (modify, add, delete, deny), Granularity (whole-file down to minimal edits), and Temporal (single-shot through slow-drip), then turn that space into a 23-cell matrix with 43 concrete operations on real self-state files, injected into live activity traces from a representative self-hosted agent running across distinct workload profiles. The empirical result is where the paper earns attention. A layered defense stack, described as access-control prevention on the instruction and configuration layers, workload-conditioned detection on the memory layer, and periodic backup for recovery, handles most of the matrix. Under the authors' recommended configuration, 11 attack cells become visible, 8 become conditionally detectable, and 4 remain what they call structurally indistinguishable at the OS level. Those four concentrate on memory-row writes inside operations-style workload profiles, meaning normal agent behavior and the malicious edit look the same to the kernel. The forward-looking read is what makes this worth watching. If OS-level defense really does have a structural ceiling for agent state, the useful engineering moves up the stack, toward application-layer integrity checks on memory files, canary entries, and signing of the agent's own state. Vendors shipping managed agent runtimes get a cleaner story here than teams telling customers to lock down filesystem permissions and hope. https://aiweekly.co/alerts/schmidhuber-et-al-formalize-self-state-attacks-on-ai-agents