T08 · Insecure Dependencies
- Location
SKILL.md:122- Finding
Unpinned Dependencies and Execution of Unreviewed Remote Template Code
- Content
View full analysis
``` This clones the `EasyJovayDappTemplate` from GitHub and creates the project structure: ### 2.3 Install Dependencies ```bash cd # Install base deps (Hardhat, ethers, etc.) npm install # Install OpenZeppelin contracts (almost always needed) npm install @openzeppelin/contracts # If the template has an install script: # chmod +x tools/install_deps.sh && ./tools/install_deps.sh ``` ``` Related commands elsewhere in the file also execute dependency-provided tooling: ```bash npx hardhat compile npx hardhat test ``` ### Technical Analysis The skill instructs the agent to clone a remotely maintained project template, install npm packages without exact version constraints, and optionally execute a shell script supplied by the cloned template. The reviewed skill contains neither the resulting lockfile nor the remote template and its `tools/install_deps.sh` file, so their effective behavior cannot be established from the audited artifact. An npm installation can execute package lifecycle hooks such as `preinstall`, `install`, and `postinstall`. Likewise, granting execute permission to and invoking `tools/install_deps.sh` permits the script to run arbitrary commands under the current user's account. Mutable package versions and mutable template branches allow executable content to change after this skill has been reviewed. Use of `npx` adds another supply-chain concern if the requested executable is not already installed locally, because `npx` may offer to download and execute a package from the configured npm registry. There is no evidence that the currently documented packages or remote template are malicious. The vu ...[truncated 1719 chars]- Remediation
View remediation
