T08 · Insecure Dependencies
- Location
references/install-and-invoke.md:13- Finding
Unpinned npm Package Installation and Immediate Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent obclip usage guide, but it asks users to install and run mutable remote code and use authenticated browser profiles without enough scoping safeguards.
Review this skill before installing. Prefer a pinned, reviewed @harris7/obclip version instead of bare npm or npx commands; avoid installing from a mutable main branch; use a dedicated browser profile with only the minimum login state needed; and confirm before clipping authenticated or private pages.
references/install-and-invoke.md:13Unpinned npm Package Installation and Immediate Execution
references/install-and-invoke.md:3Mutable Remote Skill Source Can Change After Review
The skill instructs use of npx @harris7/obclip --help without pinning a specific package version, which can fetch and execute whatever version is current at runtime. That creates a supply-chain risk: a compromised publisher account, malicious newly published version, or unexpected breaking change could cause unreviewed code execution on the analyst's machine.
The skill enables implicit invocation while using very broad routing language ('install or run obclip' and 'capture a target page into a note') without clear constraints on when it should be triggered. Because this skill can install packages and operate a browser-based clipping tool against arbitrary target pages, overly broad auto-invocation increases the chance of unintended execution on untrusted content or in contexts where the user did not explicitly consent.
The recipe instructs users to operate against a logged-in social page using a real Chromium profile, but it does not warn that authenticated browser profiles may contain cookies, session tokens, history, and other sensitive data. In a skill that guides browser automation, omitting this privacy warning increases the chance that users reuse a personal profile and unintentionally expose or persist sensitive account data during automation.
Using npx @harris7/obclip without a pinned version causes execution of whatever package version is current at invocation time. That creates a supply-chain risk: a compromised maintainer account, malicious new release, or breaking update could execute arbitrary code on the user's machine during install or runtime.
The unpinned npx @harris7/obclip invocation allows fetching and running the latest published package version each time. In a skill whose purpose is to instruct installation and operation of a CLI, this makes the risk more relevant because users are explicitly encouraged to execute the command, increasing exposure to dependency hijacking or malicious updates.
Using npx @harris7/obclip --help as a verification step still executes code from an unpinned package source, so even the 'safe check' can trigger arbitrary code execution from a newly published or compromised version. Because this step is presented as routine verification before real use, it may be run frequently and with lowered user suspicion.
The troubleshooting guidance recommends running npx @harris7/obclip without a pinned version, which causes npm to resolve and execute the latest published package at runtime. This introduces supply-chain risk because a compromised publisher account, malicious new release, or dependency hijack could result in arbitrary code execution on the user's machine.
This markdown recipe demonstrates use of --output to save content into a local directory, but the surrounding text does not warn that running the command will create files on disk and may affect local data organization. For markdown files, SQP-2 applies when descriptions omit warnings about behaviors that affect user data or system integrity.