T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned and Inconsistently Named npm Packages Create a Supply-Chain Execution Risk
- Content
View full analysis
=18.0.0" }, "installation": { "npm": "npm install -g scrapeless-scraping-browser" } ``` ### Technical Analysis The skill authorizes execution through `npx` without pinning a package version or package integrity hash. Depending on the local npm cache and `npx` behavior, invoking an unavailable package can retrieve its current release from the configured npm registry and execute its package entry point. Consequently, the code executed at invocation time can differ from the code that was reviewed. The package identity is also inconsistent: - `SKILL.md` authorizes or updates `scrapeless-scraping-browser-skills`. - `skill.json` authorizes and installs `scrapeless-scraping-browser`. This inconsistency makes it unclear which package is authoritative and increases the chance of installing or executing the wrong package. If one name is obsolete, unintended, abandoned, or later acquired by another publisher, it can become a dependency-confusion or package-takeover vector. No lockfile, exact version, resolved artifact, or integrity digest is present in the audited project to bind execution to a reviewed release. ### Attack Path 1. An attacker compromises the publisher account or obtains control of one of the inconsistently referenced npm package names. 2. The a ...[truncated 1313 chars]- Remediation
View remediation
