T02 · Agent Memory Poisoning
- Location
references/agents-md.txt:43- Finding
Persistent Agent Memory Can Store Untrusted Instructions and Plaintext Credential Notes
- Content
View full analysis
Brain** ### Recommended Structure workspace/ ├── AGENTS.md # This file - rules and practices ├── MEMORY.md # Long-term curated memory ├── TOOLS.md # Local tool notes (credentials, quirks, fixes) └── memory/ └── YYYY-MM-DD.md # Daily logs ``` ### Technical Analysis The template directs an AI Agent to persist information across sessions without requiring content validation or explicit user authorization for each write. Because `AGENTS.md`, `MEMORY.md`, and related files may be consumed by future Agent sessions, untrusted content written into them can continue influencing behavior after the original interaction ends. The reference to `TOOLS.md` as a location for “credentials” also encourages sensitive information to be stored in plaintext within the workspace. Such files may be indexed by development tools, copied into backups, included in support bundles, or accidentally committed to version control. Persistent memory is not necessary for the Skill’s primary function of supplying coding conventions. The behavior therefore exceeds the minimum privileges required for an editor-rules template. ### Attack Path 1. A user copies the template into a project as `AGENTS.md`. 2. The Agent treats the memory-writing instructions as mandatory workspace policy. 3. Untrusted project content, tool output, or a user-supplied instruction asks the Agent to “remember” attacker-controlled ...[truncated 870 chars]- Remediation
View remediation
