T08 · Insecure Dependencies
- Location
SKILL.md:22- Finding
Unpinned npm Dependency for Browser Automation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 22–26
Vulnerability Type: Unpinned third-party dependency
Risk Level: Mediumyaml install: - kind: node package: "@playwright/mcp" bins: ["playwright-cli"] label: "Install Playwright CLI (npm)"Technical Analysis
The skill instructs the environment to install
@playwright/mcpwithout specifying an exact version or integrity hash. Consequently, installation may resolve to whichever release is current at that time rather than the release originally reviewed.This creates a supply-chain trust gap: a compromised maintainer account, malicious package release, or unexpected upstream change could introduce code that was not present during the skill audit. Because the package provides browser automation used for authenticated Reddit operations, compromised dependency code could potentially interact with the browser session and access environment data available to the process.
No evidence indicates that the currently named package is malicious. The vulnerability is the mutable, unverified dependency resolution mechanism.
Attack Path
- An attacker compromises the upstream package publication process or publishes a malicious future release under the legitimate package name.
- A user installs or enables the skill after that release becomes the version selected by npm.
- The skill installer retrieves the mutable package version because no exact version or integrity constraint is defined.
- Malicious installation or runtime code executes with the privileges granted to the package manager or skill process.
- The compromised component may inspect accessible environment variables, interfere with browser automation, or alter authenticated Reddit actions.
Impact Assessment
Exploitation could provide code execution with the privileges of the user or service installing and running the dependency. The practical scope may in ...[truncated 449 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
@playwright/mcpto a reviewed, exact version rather than relying on mutable default resolution. - Use a committed lockfile and enforce reproducible, frozen-lockfile installation where the skill platform supports it.
- Record and verify package integrity hashes or signatures before installation.
- Restrict installation to the official npm registry and disable unexpected lifecycle scripts when operationally feasible.
- Review package provenance, maintainers, release notes, and dependency changes before updating the pinned version.
- Run browser automation with least privilege, exposing only the credentials and filesystem paths required for the task.
- Prefer short-lived Reddit OAuth tokens over account passwords if supported by the execution architecture.
- Pin