T09 · Insecure Skill Coding Practices
- Location
SKILL.md:7- Finding
Plaintext Persistence of Potentially Sensitive Personal Information
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:7-20; related sensitive-data collection instructions appear atSKILL.md:44-57andSKILL.md:59-76
Vulnerability Type: Plaintext storage of sensitive personal data
Risk Level: MediumEvidence
markdown ## Core Behavior - Help user log what they're grateful for - Surface patterns and insights over time - Help identify gratitude when they're stuck - Create `~/gratitude/` as workspace ## File Structure~/gratitude/ ├── log/ │ └── 2024/ ├── patterns.md ├── favorites.md └── practice.md
text The types of information intended for collection and analysis include:
markdown Categories to explore: - People, relationships - Health, body - Home, comfort, safety - Work, progress, learning - Nature, beauty - Small pleasuresmarkdown ## People Mentioned Most - Sarah: 12 times - Mom: 8 times - Work team: 6 times ## Insights - You notice nature more on weekends - Productivity gratitude peaks midweek - Social connection is core themeTechnical Analysis
The Skill instructs the Agent to create a persistent journal under
~/gratitude/and store entries, named individuals, health-related observations, preferences, favorites, and inferred behavioral patterns in ordinary Markdown files. It does not require owner-only file permissions, encryption, informed consent before persistence, data minimization, retention limits, or secure deletion.Consequently, file permissions depend on the host environment's default umask and directory configuration. The journal may also be included automatically in home-directory backups, indexing systems, endpoint monitoring, or synchronization services. Derived files such as
patterns.mdconcentrate information about relationships, routines, health, and emotional experiences, potentially making disclosure more harmful than exposure of an isolated entry.Atta
...[truncated 1329 chars]
- Remediation
View remediation
Remediation Suggestions
- Clearly notify users before the first write that journal entries will be stored locally in plaintext, and obtain explicit consent.
- Create
~/gratitude/with owner-only permissions, such as mode0700, and journal files with mode0600where the operating system supports POSIX permissions. - Verify existing permissions before writing and warn the user if the directory or files are accessible to other accounts.
- Offer encrypted-at-rest storage using an established platform credential store or a well-reviewed encryption mechanism.
- Minimize collection by avoiding unnecessary names, health details, and behavioral inferences unless the user explicitly requests them.
- Provide configurable retention periods and commands to review, export, redact, and securely delete stored entries and generated summaries.
- Warn users that home-directory backup, synchronization, and indexing services may copy or process the files.
- Do not include sensitive details in aggregated pattern files unless the user has explicitly enabled pattern analysis.
