T08 · Insecure Dependencies
- Location
SKILL.md:8- Finding
Unpinned and Unnecessary Third-Party Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 8-15
Vulnerability Type: Unpinned third-party dependencies and unnecessary global package installation
Risk Level: MediumVulnerable Code
yaml dependencies: npm: - "@aiagenta2z/onekey-gateway" python: - "ai-agent-marketplace" installation: npm: npm -g install @aiagenta2z/onekey-gateway python: pip install ai-agent-marketplaceTechnical Analysis
The Skill instructs users to install two third-party packages without exact version or integrity pinning. The npm package is also installed globally. Package names without fixed versions resolve to mutable releases whose contents can change after the Skill has been reviewed.
Neither bundled REST implementation imports these dependencies. The Python script uses standard-library modules, while the TypeScript script uses Node.js globals and the built-in
fetchAPI. Consequently, installing both packages is unnecessary when using the bundled scripts and exceeds the minimum dependency scope required for their declared functionality.No evidence establishes that either dependency is currently malicious. The vulnerability is the avoidable exposure to package compromise, malicious updates, dependency takeover, and installation lifecycle scripts.
Attack Path
- An attacker compromises a listed package, its publisher account, or its package-registry distribution channel.
- The attacker publishes a malicious release or modifies an otherwise trusted release.
- A user follows the documented installation commands without a pinned version or integrity constraint.
- The package manager resolves and downloads the attacker-controlled release.
- Package installation or lifecycle hooks execute with the installing user's privileges.
- For the global npm installation, attacker-controlled files may be placed in global package and executable locations, increasing the affected sys ...[truncated 608 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove both dependency requirements when users invoke the included Python or TypeScript REST scripts, because those scripts do not import the listed packages.
- Document the OneKey CLI package separately as an optional dependency rather than a requirement for all usage paths.
- Pin every necessary dependency to an exact, reviewed version rather than allowing mutable latest-version resolution.
- Use package-manager lockfiles and integrity hashes where supported, and verify packages against trusted registry metadata.
- Avoid global npm installation. Prefer a project-local installation with a locked dependency tree and invoke the CLI through the local package runner.
- Review package provenance, maintainers, lifecycle scripts, transitive dependencies, and published artifacts before approving updates.
- Install dependencies without elevated privileges and in an isolated environment or container where practical.
