T02 · Agent Memory Poisoning
- Location
SKILL.md:80- Finding
Persistent Storage and Cross-Session Reuse of User-Provided Pet Information
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 80–83
Vulnerability Type: Persistent agent memory modification
Risk Level: LowComplete relevant snippet, rendered in English:
markdown ## User Information Memory Rules - Pet information (name, breed, age, and personality traits) is recorded only in MEMORY.md and not in the skill file. - When the user's pet information is known, proactively associate it with the conversation (for example, if the user mentions "Kimi," know that he is a male Maine Coon).Technical Analysis
The skill explicitly instructs the agent to write user-provided information into
MEMORY.mdand automatically reuse that information in later interactions. This introduces persistent state beyond the immediate pet-care request.The instructions do not require informed user consent before persistence, define a retention period, limit when the stored profile may be reused, or provide mechanisms to inspect, correct, and delete the retained information. Consequently, ordinary conversational answers can become a persistent user profile without a clear indication that storage is occurring.
This is categorized as
T02: Agent Memory Poisoningbecause the skill modifies long-term agent memory and causes stored, user-controlled content to influence future sessions. The behavior is less severe than persistent storage of executable instructions: the specified fields are limited to pet attributes, and no instruction-writing, code execution, credential collection, or external transmission was identified.Attack Path
- A user invokes the skill by asking a pet-related question.
- Following its interaction rules, the agent requests details such as the pet's name, breed, age, sex, or personality.
- The user supplies those details as ordinary conversational content.
- The skill directs the agent to persist the supplied information in
MEMORY.md. - During a later conversatio ...[truncated 931 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the unconditional instruction to write pet details to
MEMORY.md; keep them session-local by default. - Require explicit, informed opt-in before retaining any information beyond the current conversation.
- Clearly disclose which fields will be stored, why they are needed, how they will be reused, and how long they will be retained.
- Apply data minimization by retaining only fields necessary for a user-requested personalization feature.
- Provide users with mechanisms to inspect, correct, and delete stored pet information.
- Prevent user-supplied content from being stored as executable instructions or agent rules. Persist values only through a schema with fixed fields and strict length and type validation.
- Scope stored data to the correct user and prevent profiles from leaking between users or workspaces.
- Add expiration controls and automatically delete inactive profiles after a documented retention period.
- Record consent and memory changes in an auditable manner without logging unnecessary conversational content.
- Remove the unconditional instruction to write pet details to
