T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Runtime Execution of an Unpinned npm Package
- Content
View full analysis
[flags] --format json ``` ### Technical Analysis The skill requires every operation to execute `@lark-project/meegle@latest` through `npx`. The `latest` npm distribution tag is mutable and can resolve to a different package version each time the command runs. Consequently, the code executed at runtime is not necessarily the code that existed when the skill was audited. The project contains no lockfile, integrity hash, vendored implementation, or other mechanism that binds execution to a reviewed package artifact. Because `npx` may download and execute the resolved package, a compromised npm publisher account, malicious future release, or dependency supply-chain incident could replace the effective implementation without any modification to this skill. The CLI also processes authentication state, device authorization values, project data, and work-item modifications. A malicious package version would execute with the operating-system privileges of the agent process and could access all resources available to that account. ### Attack Path 1. An attacker compromises the npm publisher account, release pipeline, package, or one of its transitive dependencies. 2. The attacker publishes a malicious release and assigns it to the `latest` distribution tag. 3. A user requests a Meegle operation covered by this skill. 4. The agent follows the skill instructions and runs `npx @lark-project/meegle@latest`. 5. `npx` res ...[truncated 1006 chars]- Remediation
View remediation
