T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Third-Party Package Installed Globally
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its Dida365 task-management purpose, but it gives unsafe instructions for installing a global tool and handling account cookies and secrets.
Review before installing. Use a pinned, trusted version of the CLI if possible, avoid putting real cookies or OAuth secrets directly in shell commands or wrapper scripts, check where the CLI stores credentials, and rotate/revoke any cookie or secret that has been exposed in shell history, files, logs, backups, or repositories.
SKILL.md:15Unpinned Third-Party Package Installed Globally
SKILL.md:40Dida365 Session Cookie Exposed Through Command-Line Arguments
SKILL.md:96OAuth Credentials Embedded in a PATH Wrapper Script
The skill instructs users to extract a browser cookie and store authentication material via environment variables/CLI commands, but provides no warning about the sensitivity of those secrets, their storage location, shell history exposure, or the risk of account takeover if leaked. In this context, the cookie appears sufficient for authentication, so mishandling it could directly expose the user's Dida365 account.
The wrapper-script example hardcodes sensitive credentials into a shell script and tells users to place it on PATH, which can leave secrets readable by other local users, backups, repo commits, or system tooling. Embedding long-lived credentials in plaintext files materially increases the chance of credential leakage and downstream account compromise.
No suspicious patterns detected.