T09 · Insecure Skill Coding Practices
- Location
SKILL.md:25- Finding
Authenticated Session Cookie Handling Creates Credential Exposure Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill needs review because it asks for a LinkedIn session cookie and bulk-collects personal lead data while retaining raw data and explicitly throttling to avoid detection.
Install only if you have clear authorization to collect this data and use the target sources this way. Treat LI_SESSION as a live account credential, prefer official APIs or approved data providers, revoke the session after use, and define strict limits for raw data storage, CSV sharing, retention, and deletion before running it.
SKILL.md:25Authenticated Session Cookie Handling Creates Credential Exposure Risk
SKILL.md:12Bulk Personal-Data Collection With Unbounded Raw-Data Retention
SKILL.md:48Scraping Rule Explicitly Encourages Avoidance of Platform Detection
The skill instructs users to extract and store a live LinkedIn session cookie (li_at) without clear warnings about credential sensitivity, account takeover risk, or platform-policy implications. A browser session cookie is effectively an authentication token, so mishandling it can expose the user's account and enable unauthorized scraping or impersonation.
The usage section provides example prompts like "Generate a lead list" and "Export leads to CSV" without defining exact trigger phrases, constraints, or exclusion conditions. In a markdown skill description, this can make activation scope ambiguous because these requests resemble common business requests rather than narrowly scoped invocations.
No suspicious patterns detected.