T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned Globally Installed Browser-Automation Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 13–15
Vulnerability Type: Unpinned third-party dependency with global installation and browser integration
Risk Level: MediumVulnerable Code Snippet
markdown - `dokobot` CLI installed globally: `npm install -g @dokobot/cli` - Chrome browser with Dokobot extension installed - Local bridge running: `dokobot install-bridge` (one-time setup)Technical Analysis
The skill directs users or agents to install the latest available version of
@dokobot/cliglobally and then execute its bridge installer. It does not specify an exact reviewed version, integrity hash, lockfile, trusted registry configuration, or package verification procedure.An npm package can execute package lifecycle code during installation. A global installation makes the package's executable available throughout the user's environment. Running
dokobot install-bridgeintroduces an additional integration point between locally executed third-party code and Chrome. Because the stated purpose includes reading pages through an active browser, this integration may interact with content accessible to the current browser profile, including authenticated pages.The project contains no evidence that
@dokobot/cliis currently malicious. The issue is the unsafe dependency acquisition and installation pattern, which exposes users to a compromised, hijacked, or unexpectedly changed future package release.Attack Path
- An attacker compromises the package publisher, npm account, distribution channel, or a future package release.
- The attacker publishes malicious code under the package version resolved by the unconstrained installation command.
- A user or agent follows the skill and runs:
bash npm install -g @dokobot/cli - Malicious package lifecycle code or installed CLI code executes with the installing user's privileges.
- The user or agent runs:
bash dokobot install-bridge
6 ...[truncated 1073 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin the CLI to an exact, reviewed version rather than resolving the latest release:
bash npm install --global --ignore-scripts @dokobot/cli@<reviewed-exact-version>Only use
--ignore-scriptsif the reviewed installation process supports it. -
Record and verify the package's expected integrity digest before installation. Maintain a lockfile or an internally approved dependency manifest where practical.
-
Document the authoritative npm package, publisher identity, source repository, Chrome extension listing, and bridge distribution source so users can detect typosquatting or unofficial components.
-
Prefer a project-local or isolated installation over a global installation. Run the CLI in a restricted container, sandbox, dedicated operating-system account, or similarly constrained environment.
-
Use a dedicated Chrome profile that contains no unrelated authenticated sessions, saved passwords, sensitive extensions, or confidential browsing data.
-
Review the CLI, extension permissions, bridge behavior, lifecycle scripts, and outbound network destinations before approving a version.
-
Apply an explicit update policy. Do not automatically adopt new releases; review and approve each upgrade before deployment.
-
Restrict the URLs and browser sessions the automation component may access, and close sessions when the requested task is complete.
-