T09 · Insecure Skill Coding Practices
- Location
SKILL.md:135- Finding
Authentication State Stored at a Predictable Shared Temporary Path
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent browser automation helper, but it gives broad browser control and documents reusable authentication state in a way users should review carefully before installing.
Install only if you intend to give the agent broad browser automation authority. Avoid using shared or sensitive accounts unless necessary, prefer isolated sessions, wipe state after use, and do not save auth state to /tmp or other shared paths; treat exported auth-state files like passwords.
SKILL.md:135Authentication State Stored at a Predictable Shared Temporary Path
The skill advertises very broad trigger phrases such as 'check the page', 'QA', 'healthcheck', and effectively any task requiring a real browser. This can cause unintended invocation on common user requests, expanding the skill's reach into workflows involving authenticated browsing, form filling, uploads, and in-page code evaluation, which increases the chance of data exposure or unsafe actions being performed without explicit user intent.
The documentation highlights persistent session state, including cookies, localStorage, and auth tokens, but does not prominently warn that these artifacts are sensitive credentials. In this skill context, persistence across commands and sessions makes accidental reuse, cross-task contamination, or unsafe handling of authenticated state more likely.
The examples directly show saving and loading authentication state from a file without stating that the file may contain bearer-equivalent session material. An agent or user could treat /tmp/auth.json as routine output, leaving reusable authenticated sessions on disk where other processes or users may access them.
No suspicious patterns detected.