T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Globally Installed Dependency with Authenticated Browser Access
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 16-19
Vulnerability Type: Unpinned third-party dependency and unaudited browser extension
Risk Level: MediumRelevant code snippet:
bash npm install -g @jackwener/opencliThe same prerequisite section instructs the user to load the package's
extension/directory as an unpacked Chrome extension and states that all commands depend on cookie authentication.Technical Analysis
The skill requires users to install the latest available version of
@jackwener/opencliglobally without specifying an audited version or package integrity value. A global npm installation can run package lifecycle scripts and places executable code in the user's global environment.The installed component is also expected to interact with an unpacked Chrome extension and an existing Taobao-authenticated browser session. This creates a high-trust supply-chain boundary: the dependency and extension may execute locally and interact with authenticated browser state. The project does not provide a lockfile, integrity hash, reviewed source revision, extension manifest, or bundled extension source from which the required privileges could be verified.
This finding does not establish that the named dependency is malicious. The weakness is that an unpinned and externally maintained package is granted substantial trust without reproducible dependency verification.
Attack Path
- An attacker compromises the npm package, its maintainer account, publication pipeline, or a transitive dependency.
- The attacker publishes a modified release under the same package name.
- A user follows the documented global installation command, which resolves to the compromised current release.
- Malicious package code or npm lifecycle scripts execute with the installing user's privileges.
- The user loads or operates the associated unpacked browser extension.
- The compromised compo ...[truncated 915 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
@jackwener/openclito an exact, reviewed version rather than installing the latest release implicitly. - Publish and verify the expected npm integrity hash and provide a lockfile or equivalent reproducible installation mechanism.
- Link to the authoritative source repository and identify the exact reviewed commit corresponding to the pinned package version.
- Include the browser extension source and manifest in the auditable package, or provide cryptographic verification for the exact extension artifact.
- Restrict extension host permissions to the minimum required Taobao and Tmall origins, and avoid broad permissions such as access to all websites.
- Disable or separately audit npm lifecycle scripts before installation where operationally feasible.
- Prefer a project-local installation or an isolated environment over a global package installation.
- Document the browser data and account actions accessible to the extension, and require explicit user confirmation before state-changing operations.
- Conduct source and dependency review whenever the pinned package or extension version changes.
- Pin
