T08 · Insecure Dependencies
- Location
SKILL.md:41- Finding
Persistent Redirection of npm to a Third-Party Package Registry
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent Chinese OpenClaw troubleshooting guide, but it includes high-impact repair commands without enough safeguards.
Review before installing. The skill is not deceptive or self-executing, but users should avoid blindly running the sudo ownership changes, persistent npm registry change, kill -9, and OpenClaw reset commands. Prefer user-scoped Node/npm fixes, temporary registry overrides, environment variables for secrets, verified backups, and explicit rollback steps before using the higher-impact commands.
SKILL.md:41Persistent Redirection of npm to a Third-Party Package Registry
SKILL.md:33Overbroad Ownership Change Makes System-Wide Node Modules User-Writable
SKILL.md:127Destructive Database and Configuration Resets Lack Adequate Safeguards
The description and operational guidance are written entirely in Chinese, and the skill name suffix (-cn) suggests a forced locale. Under the policy, forcing a specific language without user opt-in or documented justification is a natural-language policy violation.
The skill instructs users to run a recursive sudo chown over the npm directory. Privileged ownership changes can weaken local security boundaries, mask underlying permission problems, and if paths are mistyped or altered, affect more files than intended.
# 修复 npm 权限
sudo chown -R $(whoami) ~/.npm
sudo chown -R $(whoami) /usr/local/lib/node_modules
This command recursively changes ownership of a system-wide Node modules directory using sudo, which can impact all users and packages on the machine. In a troubleshooting guide, such a fix may be copied without understanding the broader security and stability implications of modifying privileged installation paths.
# 修复 npm 权限
sudo chown -R $(whoami) ~/.npm
sudo chown -R $(whoami) /usr/local/lib/node_modules
The skill shows commands that transmit secrets to external services, including a Telegram bot token in a URL and a bearer API key in an HTTP header, without warning users about shell history, terminal logging, process inspection, or accidental sharing. While the commands are common for connectivity tests, they normalize handling credentials unsafely and can lead to token exposure.
The command sends a Telegram bot token to an external endpoint as part of the request URL. Although this is the expected API usage, presenting it without safety guidance can expose the token through shell history, copied terminal output, browser or proxy logs, and support transcripts.
# 测试连接
curl https://api.telegram.org/bot<YOUR_TOKEN>/getMe
The command transmits a live API key in an Authorization header to an external service. This is operationally normal for validation, but without warnings it can still leak through terminal recording, debug tooling, shared shell history, or copied logs.
# 验证 DeepSeek Key
curl -H "Authorization: Bearer YOUR_KEY" \
https://api.deepseek.com/v1/models
The troubleshooting guide includes destructive recovery actions such as resetting the database and configuration, but it does not clearly warn that these steps can cause irreversible data loss or service disruption. In a troubleshooting context, users may run such commands under stress and accidentally destroy working state or backups they still need.
No suspicious patterns detected.