other
- Location
SKILL.md:128- Finding
Persistent Storage of Sensitive Health and Behavioral Information Without Data-Minimization Controls
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:128-143andSKILL.md:365-370
Vulnerability Type: Excessive Sensitive Health Data Collection and Retention
Risk Level: MediumVulnerable code:
markdown ## User Preferences to Learn Over time, remember these preferences (via SkillBoss API Hub memory): **Schedule & Energy:** - Peak focus hours (morning person vs. night owl) - Typical energy patterns throughout the day - Best times for deep work vs. shallow tasks **Task Management:** - Preferred number of daily priorities (1-3 recommended) - Task/note storage location (files, apps, directories) - Preferred reminder frequency and channels **ADHD Profile:** - Diagnosed or suspected ADHD - Current treatments (medication, therapy) - for context only - Common pitfalls (social media, hyperfocus traps) - Strategies that have worked in the pastmarkdown ### Memory Usage: - Store user preferences and patterns - Remember what strategies have worked - Track routine adherence over time - Note energy patterns and triggersTechnical Analysis
The skill instructs the agent to place potentially sensitive health and behavioral information into the SkillBoss API Hub's persistent memory. The listed information includes diagnosed or suspected ADHD, medication or therapy, routine adherence, energy patterns, and emotional or behavioral triggers.
This exceeds data-minimization principles because treatment information is explicitly retained “for context only,” rather than being necessary to perform ordinary planning and task-management functions. The instructions do not require explicit informed consent before persistence, restrict which medical details may be stored, define a retention period, provide deletion procedures, or require redaction before memory writes.
This is not classified as T02 Agent Memory Poisoning because the retained content is user profile data rather than ...[truncated 1802 chars]
- Remediation
View remediation
Remediation Suggestions
- Do not persist diagnosis status, medication details, therapy details, or detailed emotional triggers by default.
- Require explicit, informed, and granular opt-in consent before storing any health-related information.
- Limit persistent memory to task-relevant operational preferences, such as preferred reminder times or checklist format.
- Store generalized preferences instead of source medical details. For example, retain “prefers short reminders” rather than the diagnosis or treatment context used to derive that preference.
- Add a pre-write review that tells the user exactly what information will be stored and allows modification or rejection.
- Define retention periods and automatically expire sensitive information when it is no longer required.
- Provide accessible commands to inspect, correct, export, and delete all stored memories.
- Redact health details from task files, calendar entries, review summaries, and integrations unless the user separately authorizes their inclusion.
- Restrict downstream task-tracker, calendar, and note-taking integrations from receiving health information by default.
- Document the memory system's access controls, encryption expectations, retention behavior, and incident-response process.