T08 · Insecure Dependencies
- Location
SKILL.md:347- Finding
Unpinned Remote Package Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 347
Vulnerability Type: Unpinned third-party package execution
Risk Level: HighVulnerable Code
bash npx -y @larksuite/openclaw-lark installTechnical Analysis
The emergency recovery procedure instructs users to execute an npm package through
npx -ywithout specifying an exact version or verifying package integrity. The-yoption automatically accepts installation prompts, while the missing version constraint causes npm to resolve a mutable package release at execution time.Consequently, the code reviewed during this audit is not necessarily the code that will execute when a user follows the instructions. If the upstream package, maintainer account, npm publication process, or dependency chain is compromised, arbitrary package lifecycle or installer code can run under the invoking user's account.
Although the scoped package name is consistent with the plugin discussed by the Skill, the project does not provide a lockfile, integrity hash, signature verification, or other mechanism for authenticating the downloaded artifact.
Attack Path
- An attacker compromises the referenced npm package, a maintainer account, or a transitive dependency.
- The attacker publishes a malicious version that remains eligible for default npm resolution.
- A user follows the documented emergency recovery procedure.
npx -yretrieves the mutable package release and automatically proceeds without an interactive approval step.- Package lifecycle hooks or the installer execute with the user's privileges.
- The malicious package can read or modify files, access environment variables and credentials available to the user, initiate network connections, or alter the OpenClaw installation.
Impact Assessment
Successful exploitation permits arbitrary code execution with the privileges of the user running the command. The affected scope can inc ...[truncated 282 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an exact, previously audited version, for example
@larksuite/openclaw-lark@X.Y.Z. - Publish and verify an expected package integrity hash or cryptographic signature before execution.
- Avoid
npx -y; retain an explicit review and confirmation step. - Use a lockfile or a trusted internal package mirror with immutable artifacts.
- Review package lifecycle scripts and the resolved dependency tree before installation.
- Execute installation with the minimum required privileges and in a restricted environment where practical.
- Document the expected publisher, package version, checksum, and verification procedure.
- Pin the dependency to an exact, previously audited version, for example
