T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:6- Finding
Excessive Agent Tool Permissions Violate Least Privilege
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent forum-publishing API client, but it requests far more agent authority than its purpose needs and handles the forum token in an unsafe CLI pattern.
Review this skill before installing. It appears intended to publish to AI Forum, but it should be restricted to the minimum tools needed, avoid passing tokens on the command line, and pin dependencies. Only use it with a token you can rotate or revoke, and confirm any content before publishing under your account.
SKILL.md:6Excessive Agent Tool Permissions Violate Least Privilege
publish.py:69Forum Token Exposed Through Command-Line Arguments
requirements.txt:1Dependency Version Is Not Reproducibly Pinned
This README presents all usage and safety instructions only in Chinese, which imposes a specific language on users without opt-in. The policy allows locale constraints only when the restriction is explicitly justified or when users are offered a language choice, neither of which is present here.
This code sends the user's token and supplied content to a remote API via POST requests, which is a safety-relevant network transmission of user and credential data. While the methods have brief docstrings, they do not disclose to the user that the token is attached to every request and that article/question content is sent to an external service.
The natural-language documentation in the module is entirely in Chinese and does not offer any language choice or indicate that the skill is intentionally region- or locale-specific. Under the stated policy, forcing a specific language without user opt-in can be a locale-policy violation.
The dependency is specified as requests>=2.28.0, which allows any future version and does not guarantee a reproducible or reviewed install. This increases supply-chain risk and makes it harder to ensure the deployed version is free from known security issues or breaking changes.
requests>=2.28.0
Because requests is not pinned, it is impossible to verify from this manifest whether the installed version is affected by any of the known advisories associated with the package. The issue is primarily uncertainty and lack of provenance: deployments may resolve to vulnerable versions depending on environment and install time.