T09 · Insecure Skill Coding Practices
- Location
MEMORY.md:3- Finding
Exact Birth Date Persisted in Plaintext Memory
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:20-23,SKILL.md:198-224, andMEMORY.md:3-11
Vulnerability Type: Plaintext storage of personal data
Risk Level: MediumThe Skill grants itself read and write access to a repository-local memory file:
yaml data_access: - path: "MEMORY.md" operations: ["read", "write"]The initial setup procedure directs the Agent to record user information in that file. The distributed
MEMORY.mdalready contains the following sensitive values:text Exact birth date: 1981-06-29 Birth year: 1981 Zodiac sign: Cancer Chinese zodiac animal: RoosterTechnical Analysis
An exact birth date is personal data that can contribute to identity verification, profiling, or correlation with information from other sources. The Skill stores this information in an unencrypted Markdown file inside the project directory.
No consent requirement, retention period, deletion procedure, access restriction, or redaction mechanism is defined. Retaining the exact date is also unnecessary after deriving the zodiac sign and Chinese zodiac animal. The packaged memory file contains a populated user record rather than an empty template, creating a risk that personal data will be copied when the project is archived, synchronized, backed up, or redistributed.
This is not evidence of network exfiltration or malicious collection. Exploitation requires an actor or integration with access to the project directory or a copy of the package.
Attack Path
- A user supplies an exact birth date for personalization.
- The Agent follows the Skill instructions and writes the date to
MEMORY.md. - The plaintext file persists across sessions in the project directory.
- The directory is read by another local user, integration, backup process, synchronization service, or package recipient.
- The actor obtains the exact birth date and associated profile information without ...[truncated 634 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the populated user record from the distributed package and replace it with an empty, synthetic template.
- Do not retain exact birth dates by default. Derive the zodiac attributes in memory and persist only the minimum necessary values, such as the selected zodiac sign and animal.
- Obtain explicit user consent before enabling persistent personalization.
- Clearly document what data is stored, why it is needed, where it is stored, and how users can inspect or delete it.
- Define a retention period and automatically delete stale profile data.
- Exclude
MEMORY.mdand similar user-state files from source control, package publication, backups, and deployment artifacts. - Where exact dates must be retained, use protected application storage with restrictive filesystem permissions and encryption at rest rather than repository-local Markdown.
- Separate templates from runtime user state so newly installed or redistributed copies cannot contain a previous user's information.
- Add a deletion workflow that removes both primary records and known cached or generated copies.
