T08 · Insecure Dependencies
- Location
README.md:12- Finding
Unpinned npx Installer and Mutable Repository Reference Enable Supply-Chain Execution
- Content
View full analysis
Vulnerability Details
File Location:
README.md:12andREADME.md:135
Vulnerability Type: Unpinned third-party installer and mutable dependency source
Risk Level: MediumVulnerable Code
bash npx skills add replynodes/replynodes-agent-skills --skill replynodes --agent openclaw --yesThe same command appears in both the installation and update instructions.
Technical Analysis
The documented command invokes the third-party
skillspackage throughnpxwithout specifying an exact package version. Depending on the local npm cache andnpxbehavior, this can download and execute the version currently resolved by the npm registry. Consequently, the executable installer may differ from the version reviewed when this skill was audited.The repository argument,
replynodes/replynodes-agent-skills, is also not tied to an immutable release tag or full commit SHA in this command. Although the README separately provides a tagged direct-Git installation example, the primarynpxinstallation and update commands do not provide equivalent source immutability.This is a supply-chain risk rather than evidence that the current repository contains malicious code. Exploitation requires compromise or malicious alteration of the externally resolved installer package, its distribution path, or the mutable repository revision.
Attack Path
- An attacker compromises the npm package resolved by
npx skills, its maintainer account, or another relevant distribution component. - Alternatively, an attacker causes the mutable repository reference to resolve to an unauthorized revision.
- A user follows the documented installation or update command.
npxretrieves and executes the externally supplied installer version with the user's local privileges.- The compromised installer can run arbitrary code within those privileges or install altered skill content.
Impact Assessment
Successful exploi ...[truncated 444 chars]
- An attacker compromises the npm package resolved by
- Remediation
View remediation
Remediation Suggestions
- Pin the npm installer to a reviewed exact version, for example by using
npx -y package-name@X.Y.Z .... - Pin the installed repository to an immutable release tag or, preferably, a full reviewed commit SHA.
- Ensure update instructions use the same immutable and version-pinned approach as installation instructions.
- Publish checksums or signatures for release artifacts and instruct users to verify them before import.
- Consider using
npm exec --package=package-name@X.Y.Z -- ...to make the selected installer version explicit. - Review each new installer and skill release before changing the pinned versions.
- Pin the npm installer to a reviewed exact version, for example by using
