T08 · Insecure Dependencies
- Location
SKILL.md:20- Finding
Unpinned Global npm Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:20-23
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
bash npm install -g seo-intel seo-intel setup # detects OpenClaw automatically, configures everythingRelated instances also recommend installing Wrangler without a pinned version:
SKILL.md:500-503AGENT_GUIDE.md:282-285
bash npm install -g wrangler wrangler login # opens browser for Cloudflare OAuthTechnical Analysis
The instructions install globally scoped npm packages using mutable package names without:
- Pinning reviewed versions
- Verifying package integrity hashes or signatures
- Using a lockfile
- Disabling or reviewing npm lifecycle scripts
- Confirming the expected registry and package provenance
An npm package can execute lifecycle scripts during installation. Because no version is specified, the command resolves to whichever release the configured registry currently identifies as latest. Consequently, the code ultimately installed and executed can differ from what was reviewed during this audit.
The audited artifact contains documentation but does not include the source code of either external package. Their runtime behavior therefore cannot be validated from this project alone. This is a supply-chain exposure, not evidence that either named package is currently malicious.
Attack Path
- An attacker compromises the publisher account, package release process, or npm registry path for one of the named packages.
- The attacker publishes a malicious release or causes a malicious version to resolve as the latest package.
- A user or agent follows the documented
npm install -gcommand. - npm downloads the mutable release and may execute its installation lifecycle scripts.
- The malicious package runs under the installing user's privileges and remains available as a globally installed executable.
- If the compromised executab ...[truncated 891 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin every installed tool to a reviewed version, for example:
bash npm install -g seo-intel@1.5.21 npm install -g wrangler@<reviewed-version> -
Publish and verify expected package integrity hashes or signed release artifacts before installation.
-
Explicitly configure the trusted registry and verify package ownership and provenance:
bash npm config get registry npm view seo-intel@1.5.21 dist.integrity repository maintainers -
Prefer project-local, lockfile-controlled dependencies over global installation where practical.
-
Review package contents and lifecycle scripts before installation. Where compatible with the package, initially install with lifecycle scripts disabled:
bash npm install --ignore-scripts -
Run installation and crawling in an isolated, least-privileged environment without unrelated credentials.
-
Keep Cloudflare authentication separate from analysis environments and require explicit human approval before live deployment.
-
Add documented version-upgrade procedures requiring source review, integrity verification, and testing before changing the pinned versions.
-
