T08 · Insecure Dependencies
- Location
SKILL.md:12- Finding
Unpinned Remote Dependencies Receive Access to an Authenticated Browser Session
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 12–22
Vulnerability Type: Unpinned and unverified third-party dependencies
Risk Level: HighVulnerable Code Snippet
bash npm install -g @jackwener/openclitext https://github.com/jackwener/openclibash opencli plugin install github:SPYQWER1/opencli-plugin-boss-geekThe surrounding instructions require the user to log in to
zhipin.comthrough Chrome and install the OpenCLI Chrome extension before installing the remote plugin.Technical Analysis
The Skill directs users to install OpenCLI globally without specifying an exact package version. It also installs a plugin directly from a mutable GitHub repository reference without pinning a reviewed commit hash, release tag, checksum, or cryptographic signature.
Consequently, the code installed when a user follows these instructions may differ from the code that existed when the Skill was audited. The plugin is intended to reuse an authenticated Chrome session and can perform security-sensitive operations such as reading conversations, greeting recruiters, and sending messages. This combination creates a supply-chain trust boundary: a compromised package registry account, GitHub account, repository, release process, or upstream dependency could introduce arbitrary code with access to both the local execution environment and the authenticated browser session.
The audit did not establish that either upstream project is currently malicious. The confirmed issue is the absence of dependency pinning and integrity verification despite the dependency's sensitive access.
Attack Path
- An attacker compromises the npm package, GitHub repository, maintainer account, release pipeline, or one of the upstream dependencies.
- The attacker publishes malicious code under the same package or repository reference.
- A user follows the Skill instructions and runs the unpinned global npm installation or mutable GitHub plugi ...[truncated 1253 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
@jackwener/openclito a specific reviewed version instead of installing the latest mutable release. - Pin the GitHub plugin to a reviewed immutable commit hash rather than the repository's default branch.
- Publish and verify cryptographic checksums or signatures for all installed artifacts.
- Review the OpenCLI and plugin source code at the pinned revisions before granting browser access.
- Document the exact permissions and browser data available to the extension and plugin.
- Use a dedicated Chrome profile containing only the BOSS Zhipin session, with unrelated accounts and extensions removed.
- Avoid global installation where possible. Run the tool in a restricted project environment, container, or sandbox with minimal filesystem and network access.
- Require explicit user confirmation before operations that send greetings or chat messages.
- Establish a controlled upgrade process in which new dependency versions and commits are reviewed and integrity metadata is updated before deployment.
- Pin
