T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Playwright Dependency Installation
- Content
View full analysis
/dev/null || npm install playwright ``` ### Technical Analysis The Skill installs `playwright` without an exact version or a lockfile. Consequently, the code downloaded and executed can change after the Skill has been reviewed. npm installation may also run package lifecycle scripts with the privileges of the Agent process. Installation takes place from the shared `/tmp` directory rather than a dedicated project directory. This makes package resolution and generated npm state less controlled and may permit interference by other local users or processes on a multi-user system. No evidence indicates that the current Playwright package is malicious. The vulnerability is the mutable, unverified dependency-installation process. ### Attack Path 1. An attacker compromises the upstream package, an associated dependency, or the relevant registry delivery path. 2. A user or Agent follows the setup instructions and executes `npm install playwright`. 3. npm resolves the latest package version because no exact version or lockfile is specified. 4. The compromised package or dependency is downloaded. 5. Malicious installation or lifecycle code executes with the permissions of the Agent account. 6. That code can access files, credentials, and network resources available to the Agent. A local attacker may also attempt to manipulate npm-related state under the shared temporary directory before installation, depending on directory permissions and the surrounding environment. ### Impact Assessment Successful exploitation could provi ...[truncated 377 chars]- Remediation
View remediation
