T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned Third-Party CLI Dependency with Access to Credentials and Cloud Resources
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:4
Vulnerability Type: Unpinned executable dependency
Risk Level: MediumVulnerable Code Snippet:
yaml metadata: {"openclaw":{"emoji":"⚡","homepage":"https://fastmode.ai","requires":{"bins":["fastmode"]},"install":[{"id":"npm","kind":"npm","package":"fastmode-cli","bins":["fastmode"]}]}}Technical Analysis
The Skill declares
fastmode-clias an npm-installed executable without specifying an exact version or an integrity digest. Consequently, installation may resolve to mutable package content published after this Skill was reviewed.The project contains only
SKILL.md; it does not include the executable implementation of the CLI. The audit therefore cannot verify how the dependency handles local files, OAuth tokens, network requests, or authenticated cloud operations. This is particularly significant because the documented CLI persists OAuth credentials in~/.fastmode/credentials.json, uploads deployment archives, and can perform project management, CMS modification, client invitation, DNS, API, and billing-related operations.This is a supply-chain weakness rather than evidence that the current npm package is malicious. Exploitation requires compromise of the package, its publisher account, the npm distribution path, or publication of an unsafe future release.
Attack Path
- An attacker compromises the
fastmode-clinpm package, its maintainer account, or another component of its release process. - The attacker publishes a modified package version containing malicious installation-time or runtime behavior.
- Because the Skill does not pin a reviewed version and integrity value, a subsequent installation resolves to the compromised release.
- The installed
fastmodeexecutable runs with the privileges of the user or Agent invoking it. - The malicious executable can attempt to read accessible local data, including the documented F ...[truncated 897 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
fastmode-clito an exact, security-reviewed version rather than allowing installation of an unspecified release. - Require verification against an expected package integrity digest or trusted lockfile.
- Publish or vendor the corresponding CLI source so its credential access, network destinations, installation hooks, and command execution behavior can be audited.
- Use reproducible builds and signed release artifacts, and document how signatures are verified before execution.
- Review dependency updates before changing the pinned version, including transitive dependencies and npm lifecycle scripts.
- Run the CLI with the minimum necessary filesystem and network privileges. Restrict access to unrelated credentials and sensitive files.
- Keep FastMode OAuth scopes limited to required project operations and provide straightforward token revocation and rotation procedures.
- Pin
