T09 · Insecure Skill Coding Practices
- Location
SKILL.md:53- Finding
Persistent Plaintext Storage of User Information and Agent Memory
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 53-60; related instructions at lines 67-68, 74, 86-91, and 96-101
Vulnerability Type: Plaintext sensitive-data storage without access, retention, or data-minimization controls
Risk Level: MediumComplete Code Snippet
The following is an English rendering of the relevant source instructions:
markdown | Level | File | Purpose | | P0 | MEMORY.md | Long-term memory and core experiences | | P1 | memory/YYYY-MM-DD.md | Daily logs | | P2 | Temporary files | Temporary storage | Memory principles: - Important decisions → MEMORY.md - Daily events → memory/YYYY-MM-DD.md - Temporary information → delete after useRelated workspace and startup instructions define
USER.mdas the user-information file, identifyMEMORY.mdas long-term memory, and require both files to be read when the agent starts.Technical Analysis
The skill establishes a persistent, file-based profiling system that stores user information, important decisions, experiences, daily events, and feedback in ordinary Markdown files. These files are subsequently loaded into the agent context during startup.
No controls are specified for:
- Obtaining explicit consent before recording information.
- Limiting which categories of user data may be retained.
- Preventing credentials, authentication tokens, private messages, or other sensitive data from being written.
- Applying restrictive filesystem permissions or encryption.
- Separating memory belonging to different users or agents.
- Expiring, reviewing, exporting, or securely deleting stored information.
- Preventing unrelated future tasks from reading retained data.
Because the design uses persistent plaintext files, any process or local account with access to the workspace may be able to inspect the retained information. Backups, synchronization tools, source-control operations, or later agent runs could also expo ...[truncated 1582 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit, informed user opt-in before enabling persistent memory.
- Define an allowlist of data categories that may be stored and prohibit passwords, access tokens, private keys, financial details, health information, and raw email content.
- Store only concise summaries necessary for an identified purpose rather than complete conversations or messages.
- Apply owner-only filesystem permissions, such as mode
0600for files and0700for memory directories. - Encrypt sensitive memory at rest using keys managed separately from the workspace.
- Isolate memory by user, agent, and tenant; never reuse a shared
USER.mdorMEMORY.md. - Establish retention periods, expiration rules, user-visible review controls, and secure deletion procedures.
- Require confirmation before promoting temporary or daily information into long-term memory.
- Treat all loaded memory as untrusted data rather than authoritative instructions, preventing stored content from controlling tools or overriding safety rules.
- Exclude memory files from source control, public archives, diagnostic bundles, and unapproved synchronization or backup systems.
