T08 · Insecure Dependencies
- Location
README.md:45- Finding
Unpinned Third-Party Package Installation and Execution
- Content
View full analysis
Vulnerability Details
File Location:
README.md:45,README.md:88,skill.md:168,api-reference.md:256,api-reference.md:294,api-reference.md:482
Vulnerability Type: Unpinned dependencies retrieved from third-party package registries
Risk Level: HighVulnerable Code
bash npx clawhub@latest install subject-librarybash pip install akshareThe same unversioned AKShare installation instruction is repeated in the Skill documentation and fallback implementation guidance.
Technical Analysis
The installation command uses
npxwith the mutable@latesttag. This causes the package manager to download and execute whichever package release is designated as latest at execution time, rather than the version reviewed during this audit.The AKShare installation instructions similarly omit an exact version, lockfile, package hash, or signature verification. Importing the resulting package executes its Python module initialization code, while package installation may also execute build-system logic.
Because the effective dependency contents can change independently of this repository, the reviewed Skill does not provide a reproducible or integrity-verified dependency chain.
Attack Path
- An attacker compromises the package publisher, registry account, package distribution infrastructure, or a transitive dependency.
- The attacker publishes a malicious release and makes it the current
latestversion, or introduces malicious code into an unpinned AKShare dependency release. - A user follows the documented
npx clawhub@latestorpip install akshareinstruction. - The package manager retrieves the malicious version because no reviewed version or integrity digest is required.
- Package installation,
npxexecution, or subsequent Python import runs attacker-controlled code. - The malicious process operates with the permissions of the user running the agent or installation command.
Impact Assessment
Succ ...[truncated 605 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed version:bash npx clawhub@<reviewed-version> install subject-library - Pin AKShare and all Python dependencies to exact versions in a lockfile or requirements file.
- Record and verify package integrity hashes, such as with pip's
--require-hashes. - Use package-lock or an equivalent npm lockfile with integrity metadata.
- Verify package publisher identity and obtain dependencies only from documented, trusted registries.
- Disable or review package lifecycle scripts where operationally possible.
- Run installation in a sandbox or least-privileged environment without access to secrets.
- Establish a dependency-update process in which new versions are reviewed and tested before their pins are changed.
- Replace
