T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party Components Installed from Mutable Remote Sources
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14–22
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumThe skill directs users to globally install an npm package, install an unspecified Chrome extension, and install a plugin directly from a mutable GitHub repository:
bash npm install -g @jackwener/openclibash opencli plugin install github:SPYQWER1/opencli-plugin-boss-jobTechnical Analysis
Neither installation command pins the dependency to a reviewed version or immutable commit. No integrity hash, checksum, or signature-verification procedure is provided. The source and version of the required Chrome extension are also unspecified.
Installing the npm package globally may expose system-level CLI resources available to the current user. The GitHub plugin reference can resolve to different content over time without any modification to this skill. Because the documented workflow reuses an authenticated Chrome session for
zhipin.com, the installed components may operate in a sensitive context containing session cookies, job-search information, recruiter conversations, and message-sending capabilities.The repository contains only
SKILL.md; therefore, there is no bundled executable code demonstrating an intentional malicious payload. The risk arises from the unpinned and insufficiently verified dependency-installation process.Attack Path
- An attacker compromises the npm publisher account, GitHub repository, release process, or distribution channel for the Chrome extension.
- The attacker publishes malicious code under the same package, repository reference, or extension identity.
- A user follows the skill instructions and installs the current mutable dependency without version or integrity verification.
- The compromised component executes in the user's environment and interacts with OpenCLI or the browser extension.
- When the user is logged i ...[truncated 987 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
@jackwener/openclito a specifically reviewed version rather than installing the latest published release. - Record and verify npm integrity metadata or an independently published cryptographic checksum before installation.
- Pin the GitHub plugin to a reviewed immutable commit hash or signed release instead of a mutable repository reference.
- Document the official Chrome extension source, publisher identity, exact version, required permissions, and signature-verification procedure.
- Review the source code of OpenCLI, the plugin, and the extension together because the security boundary spans all three components.
- Require explicit user confirmation before reading conversations, greeting recruiters, or sending messages.
- Grant the extension only the minimum host permissions needed for
zhipin.com, and avoid access to unrelated sites or browser data. - Run the CLI with an unprivileged user account and avoid elevated installation or execution where possible.
- Maintain a dependency lock or manifest containing approved versions, commit hashes, checksums, and review dates.
- Re-review dependencies before updating any pinned version or commit.
- Pin
