T08 · Insecure Dependencies
- Location
SKILL.md:12- Finding
Unpinned Executable npm Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 12–15
Vulnerability Type: Unpinned third-party executable dependency
Risk Level: Mediumyaml install: - kind: node package: "@baijimu/cli" bins: [baijimu]Technical Analysis
The Skill declares installation of the executable npm package
@baijimu/cliwithout specifying an exact version, lockfile, or integrity digest. Package resolution can therefore select mutable registry content that was not included in or verified by this audit. The package implementation and any installation lifecycle scripts are absent from the audited project.This creates a supply-chain trust boundary: compromise of the package, its maintainer account, registry resolution, or a transitive dependency could cause attacker-controlled code to execute when the dependency is installed or invoked.
Attack Path
- An attacker compromises the npm package, a maintainer account, registry delivery, or a dependency in its supply chain.
- The attacker publishes or causes resolution to a malicious release.
- A user or Agent loads the Skill and installs the dependency using the unversioned package declaration.
- npm resolves the attacker-controlled version.
- Malicious lifecycle-script or CLI code executes with the privileges of the installing process.
- The code may access local files and credentials or interfere with authenticated Baijimu publication and Runtime operations available to that process.
Impact Assessment
Successful exploitation could obtain code execution under the installing user's privileges. The accessible scope may include local project data, environment variables, CLI credentials, authenticated Baijimu workspaces, and Bundle publication or Runtime operations authorized to that identity. No malicious payload was present in the audited repository itself; exploitation depends on compromise or unsafe resolution of the external dependency.
- Remediation
View remediation
Remediation Suggestions
- Pin
@baijimu/clito a reviewed, exact version rather than using an unconstrained package reference. - Record and verify the package integrity digest through an appropriate lockfile or equivalent installation metadata.
- Use an explicitly trusted npm registry and enforce registry provenance controls where supported.
- Review the pinned package, its transitive dependency graph, and any npm lifecycle scripts before deployment.
- Disable lifecycle scripts during installation where they are not required.
- Run the CLI with least privilege and isolate it from credentials, files, and environments unrelated to the Bundle task.
- Establish an update process that separately reviews and verifies each dependency version change before adoption.
- Pin
