T09 · Insecure Skill Coding Practices
- Location
SKILL.md:29- Finding
Plaintext Storage of Sensitive Third-Party and Preparedness Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 29-49
Vulnerability Type: Plaintext sensitive-data storage and unsafe filename construction
Risk Level: MediumVulnerable Code Snippet:
markdown **Agent action**: Create a file `nuclear-map.md` with columns: Name/Contact, Asset/Skill, Distance, Trust Level (low/medium/high), Last Contact Date. Fill it only with people you can reach organically — no online strangers. **Agent action**: Use this exact opener script: “With everything going on in the world lately, I’ve been thinking about how handy it would be to know a few neighbors who could check on each other if something big ever happened. You seem like someone who’s prepared — ever thought about that?” Listen more than you speak. Log every interaction in `contact-[name].md`. **Agent action**: Use this script: “If anything serious ever hits — power outage, storm, or worse — would you be open to a quick group text or knock to share what we each know and maybe use each other’s basements or supplies? I’d do the same for you.” Get verbal agreement and exchange emergency phone numbers. Note the agreement date in their file. **Agent action**: Open `nuclear-map.md`, update trust levels and assets, and schedule one low-key check-in per month with at least two people.Technical Analysis
The Skill requires an agent to persist names, contact details, approximate locations, trust assessments, emergency capabilities, preparedness assets, interaction histories, and agreement dates in predictable Markdown files. These instructions do not specify encryption, restrictive file permissions, data minimization, consent documentation, retention limits, secure deletion, or exclusion from backups and source control.
The dynamic filename pattern
contact-[name].mdalso lacks filename sanitization requirements. If a name or identifier contains path separators or traversal sequences, an implementation that performs direc ...[truncated 1855 chars]- Remediation
View remediation
Remediation Suggestions
- Obtain explicit, informed consent before recording any third party's personal or preparedness information.
- Minimize stored data. Avoid detailed supply inventories, subjective trust ratings, precise locations, and complete phone numbers unless strictly necessary.
- Store sensitive records in an encrypted location with permissions restricted to the current user.
- Prevent automatic inclusion in source control, cloud synchronization, telemetry, logs, and unencrypted backups.
- Define retention periods and provide procedures for reviewing, correcting, exporting, and securely deleting records.
- Replace names in filenames with random identifiers or sanitized, application-generated identifiers.
- Reject path separators, traversal sequences, control characters, reserved names, and unexpected filename characters.
- Resolve the final path and verify that it remains inside a dedicated storage directory before writing.
- Document that verbal participation in an emergency pact does not automatically constitute consent to maintain a detailed digital profile.
