T08 · Insecure Dependencies
- Location
SKILL.md:8- Finding
Unpinned Global Installation of a Third-Party npm Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 8
Vulnerability Type: Unpinned and globally installed third-party dependency
Risk Level: MediumVulnerable Code Snippet:
bash npm install -g aip-openclawTechnical Analysis
The setup instructions install
aip-openclawglobally without specifying an audited version or verifying package integrity. Consequently, npm resolves the mutable package version associated with the default distribution tag at installation time rather than a release reviewed with this skill.npm packages can define lifecycle scripts that run during installation. If the package, its maintainer account, or one of its transitive dependencies is compromised, installation could execute attacker-controlled code. The global installation option also exposes system-wide npm directories and creates commands available throughout the user's environment.
The project only contains
SKILL.md; the package implementation and its claims concerning signature verification, capability enforcement, and audit logging are not present and therefore could not be independently validated during this audit.Attack Path
- An attacker compromises the
aip-openclawnpm package, its publisher account, or a transitive dependency, or causes an unsafe release to become the version selected by npm. - A user follows the documented
npm install -g aip-openclawinstruction. - npm downloads the mutable package release and its dependency tree from the configured registry.
- Malicious lifecycle scripts may execute during installation, or malicious package logic may execute when the installed command is later invoked.
- The payload operates with the permissions of the account running npm and may modify resources accessible to that account.
Impact Assessment
Successful exploitation could permit arbitrary command execution with the installing user's privileges. The attacker could access or m ...[truncated 389 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the installation to a specifically reviewed package version rather than relying on the mutable latest release.
- Publish and verify the expected package integrity digest and document how the npm artifact is tied to the reviewed source revision.
- Prefer a project-local installation with a lockfile over global installation when global availability is not essential.
- Review the package, its lifecycle scripts, and its complete transitive dependency tree before recommending installation.
- Consider initially installing with lifecycle scripts disabled, then enable only scripts that have been explicitly reviewed.
- Do not run the installation as
rootor throughsudo; use a least-privileged account and a controlled npm prefix. - Use automated dependency monitoring, provenance verification, and periodic re-auditing for every approved version.
