T09 · Insecure Skill Coding Practices
- Location
SKILL.md:5- Finding
Hardcoded Precise Residential Location in Distributable Skill Metadata
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 5–7
Vulnerability Type: Plaintext sensitive personal data exposure
Risk Level: MediumVulnerable Code:
yaml metadata: address: "102 Saboori Enclave Whitefields" pincode: "500081" location: "Hyderabad"Technical Analysis
The skill stores a precise residential address directly in plaintext metadata. This information is available to anyone who can access, distribute, inspect, archive, or index the skill package. The workflow only needs a delivery pincode to search for product availability, so retaining the complete address violates data-minimization principles.
No access control, runtime prompt, environment-based configuration, or redaction mechanism protects the address. Because it is static package content, deleting the address from an individual runtime session would not remove it from existing copies, repositories, archives, or caches.
Attack Path
- An attacker obtains access to the skill package or a repository containing it.
- The attacker opens
SKILL.mdwithout needing to execute the skill. - The attacker reads the
metadatasection and extracts the precise address, pincode, and city. - The attacker correlates that information with other available records or uses it for profiling, phishing, social engineering, or physical-location targeting.
Impact Assessment
Exploitation requires only read access to the distributed project and grants no direct system privileges. However, it exposes persistent personal location information beyond what is necessary for the skill's functionality. The disclosure scope includes every person or service that receives, stores, logs, indexes, or republishes the skill package.
- Remediation
View remediation
Remediation Suggestions
- Remove the full street address from the skill metadata.
- Request the minimum required location information at runtime, preferably only the pincode needed for product availability checks.
- Store user-specific location data outside distributable skill files and prevent it from being committed to source control.
- If persistent location configuration is essential, use access-controlled local configuration and document its retention policy.
- Review repository history, published packages, caches, and backups for previous copies of the exposed address and remove them where feasible.
- Add automated secret and sensitive-data scanning for addresses, phone numbers, account identifiers, and other personal information before publication.
