T09 · Insecure Skill Coding Practices
- Location
scripts/login.py:4- Finding
Reusable Authentication State Stored in a Predictable Plaintext Project File
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill appears to do what it says, but it stores a reusable Xiaohongshu login session and can publish publicly without a final confirmation step.
Install only if you are comfortable granting this skill access to a Xiaohongshu creator session and letting it publish the supplied title, text, and files. Treat state.json as a sensitive login token: do not share, sync, archive, or commit it, and delete or rotate the session when you are done. Review the generated post in the visible browser before relying on the automation.
scripts/login.py:4Reusable Authentication State Stored in a Predictable Plaintext Project File
The skill metadata and description present this as a straightforward publishing automation, but the documented setup also includes a separate login flow that captures and stores authenticated browser session state in state.json. That is security-relevant behavior because persisted session artifacts can grant account access if mishandled, and the need for manual login contradicts the stated automation model, reducing transparency for users making trust decisions.
The script automatically clicks the Xiaohongshu publish button and completes a public posting flow without any explicit confirmation, warning, or dry-run step immediately before publication. In an agent setting, this creates a real risk of unintended public disclosure, accidental posting of sensitive media/text, or abuse if upstream inputs are manipulated.