T08 · Insecure Dependencies
- Location
README.md:22- Finding
Unpinned Package Execution in Installation Command
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 22–26
Vulnerability Type: Supply-chain risk from an unpinned executable package and mutable remote source
Risk Level: MediumVulnerable Code:
bash npx add https://github.com/wpank/ai/tree/main/skills/design-systems/animated-financial-displayTechnical Analysis
The documented installation command invokes
npxwith the unversioned package nameadd. If that package is not already installed locally,npxmay retrieve it from the configured npm registry and execute its package entry point with the current user's privileges.Neither the executable package nor the Skill source is pinned to an immutable version. The GitHub URL references the mutable
mainbranch instead of a reviewed commit SHA or integrity-verified release. Therefore, the code executed or installed later can differ from the content audited in this project.This is an insecure dependency and installation pattern. The audited repository itself contains only documentation and example UI code; no malicious script was found in the repository.
Attack Path
- An attacker compromises the npm package, its publisher account, the package registry path, or the referenced GitHub repository.
- The attacker publishes a malicious package version or replaces content reachable through the mutable
mainbranch. - A user follows the documented installation instructions and runs the
npx add ...command. npxdownloads and executes the current package implementation.- The malicious installer executes under the user's account and can modify files or access resources available to that account.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user running the installation command. Potential scope includes reading or modifying user-accessible project files, environment variables, credentials, and configuration; maki ...[truncated 221 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the ambiguous
npx addinvocation with a trusted installer pinned to an exact package version. - Pin the remote Skill source to a reviewed Git commit SHA rather than the mutable
mainbranch. - Where supported, enforce package integrity using a lockfile and cryptographic integrity hashes.
- Prefer a verified release artifact with a published checksum or signature.
- Use
npx --no-installwhen execution must be limited to a dependency already installed and reviewed locally. - Alternatively, provide manual installation instructions that download reviewed files without executing a third-party npm package.
- Advise users not to run installation commands with administrative privileges and to inspect remote content before installation.
- Replace the ambiguous
