T08 · Insecure Dependencies
- Location
SKILL.md:134- Finding
Unpinned npm Package Is Downloaded and Executed with Access to Sensitive OpenClaw Data
- Content
View full analysis
``` ### CVE Detection Only ```bash npx hackmyagent scan --cve ~/.openclaw ``` ### Configuration Audit ```bash npx hackmyagent audit ~/.openclaw/config.json5 ``` ### Generate Security Report ```bash npx hackmyagent secure ~/.openclaw --format html --output security-report.html ``` ``` ### Technical Analysis The Skill instructs the agent to execute `npx hackmyagent` without an exact package version, lockfile, integrity hash, or verified local installation. If the package is not already available locally, `npx` can resolve and download it from the configured npm registry before executing its CLI. Consequently, the code executed by this Skill can change after the Skill itself has been reviewed. This behavior conflicts with the frontmatter declaration `network: []` and with the statements that the Skill “runs entirely locally” and makes “no external API calls.” Package resolution and retrieval may require network access. More importantly, the downloaded package is executed with the permissions of the agent process and is explicitly given sensitive paths such as `~/.openclaw` and `~/.openclaw/config.json5`. The scanner legitimately needs read access to OpenClaw configuration for its declared auditing function. However, giving a mutable, remotely resolved package that access is not the minimum-risk implementation. A compromised npm release, maintainer account, registry, dependency, or local npm registry configuration could turn the security scan into arbitrary code execution. The reviewed Markdown does not prove that the current `hackmyagent` packag ...[truncated 2325 chars]- Remediation
View remediation
