New paper defines self-state attacks, showing OS defenses leave four agent-memory cases indistinguishable

Justgototheeffinmoon · reddit · 2026-07-22

A new arXiv paper formalizes self-state attacks: a threat class where AI agents are compromised through their own memory/configuration files rather than classic prompt injection. The authors argue that because self-hosted agents read and write their own state to operate, an attacker can exploit legitimate OS-level file and syscall behavior to poison that state.

The paper maps the space across four axes — target (instruction, memory, configuration), mechanism (modify/add/delete/deny), granularity (whole-file to minimal edits), and time (single-shot to slow-drip) — and turns it into a 23-cell matrix with 43 concrete operations tested against live traces from a representative self-hosted agent.

Key findings:

The paper's main implication is that OS hardening alone has a ceiling; stronger defenses likely need application-layer integrity checks, canary entries, and signed agent state.

Original post →

More from Safety

Safety channel →