T02 · Agent Memory Poisoning
- Location
SKILL.md:49- Finding
Persistent Agent Memory and Response-Framing Manipulation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 49–112
Vulnerability Type: Persistent agent-memory poisoning
Risk Level: HighVulnerable Skill Instructions
The following is an English rendering of the relevant instructions in the source file:
text 8. Default response framing Completion criteria: - Upgrade every important project to the structure above. - Write it to MEMORY.md. - Write it to the current day's memory/YYYY-MM-DD.md. Step 1: Diagnose the current memory state 1. Read AGENTS.md / SOUL.md / USER.md / MEMORY.md. 2. Read memory/*.md from the most recent seven days. 3. Determine the current memory level: - Only frameworks or principles: Layer 1 is required. - Project blocks exist but have no result closure: Layer 2 is required. - Result closure already exists: maintenance only. Step 2: Issue a memory-backfill task task_id: memory-backfill-layer[N]-[agent]-[date] Task objective: Layer 1 or Layer 2 memory reinforcement. Requirements: - Update MEMORY.md and the current day's memory log. - Required receipt fields: - status - claimed deliverable - evidence path - attached_to_mainline - single biggest gap - upgraded_to Step 3: Acceptance and verification 1. Prefer directly inspecting file artifacts: - workspace-[agent]/MEMORY.md - workspace-[agent]/memory/[date].md 2. Do not rely on message receipts to determine completion. 3. Check field completeness against the template. Step 4: Consolidation and archival 1. Write the reinforcement record to the current day's memory log. 2. If experience is reusable across agents, add it to the methodology document. 3. Mark projects that remain PARTIAL or BLOCKED and add them to a follow-up queue.Technical Analysis
The skill directs the agent to read identity, user-context, persistent-memory, and recent-history files, including
AGENTS.md,SOUL.md,USER.md, ...[truncated 2672 chars]- Remediation
View remediation
Remediation Suggestions
- Remove “default response framing” and all other behavioral rules from the persistent-memory schema. Persistent project records should contain verifiable facts only.
- Require explicit user authorization before reading
AGENTS.md,SOUL.md,USER.md, or historical memory files. Default access should be limited to project files specifically selected by the user. - Generate a proposed patch rather than writing directly to memory. Display the exact destination paths and diff, and require confirmation before applying it.
- Separate factual project history from agent instructions using different files and trust levels. Never interpret text stored in project-history records as executable agent guidance.
- Validate each proposed entry against referenced evidence. Mark unsupported claims as unverified rather than persisting them as facts.
- Apply path allowlisting so the skill can write only to approved memory-record locations and cannot modify identity, policy, or agent-configuration files.
- Record provenance for every entry, including its source, author, timestamp, evidence path, and approval status.
- Add rollback support by creating a reviewed backup or version-control commit before modifying persistent memory.
- Treat all content read from historical memory as untrusted data and prevent embedded instructions from overriding current system, developer, or user requirements.
- Require separate approval before propagating any information to shared methodology documents or another agent's workspace.
