T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:43- Finding
Mutable Remote Package Is Downloaded and Executed Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:43
Vulnerability Type: Remote payload retrieval and supply-chain risk
Risk Level: HighEvidence
bash npx wolverine-ai@latest --setup-clawThe package is also declared without an exact version:
yaml install: - kind: node package: wolverine-ai bins: - wolverine - wolverine-clawTechnical Analysis
The documented setup command instructs users to download and execute the package version associated with the mutable
latestnpm tag. The effective executable payload can therefore change after this Skill has been reviewed.The project contains only
SKILL.md; it does not include the package implementation, a lockfile, an integrity hash, or vendored source through which the downloaded code could be verified. Any lifecycle scripts or transitive dependencies associated with the current package release may execute under the invoking user's account.This behavior exceeds the minimum privileges needed for deterministic installation because an audited, exact package version could be used instead of a mutable release tag.
Attack Path
- An attacker compromises the npm publisher account, the package, or one of its dependencies.
- The attacker publishes a malicious release and assigns it to the
latesttag. - A user follows the documented Quick Start command.
npxdownloads and executes the attacker-controlled release.- The payload runs with the user's permissions and may access the workspace, environment variables, API credentials, files, and processes available to that account.
Impact Assessment
Successful exploitation could result in arbitrary code execution with the privileges of the user running
npx. The accessible scope may include the OpenClaw workspace,ANTHROPIC_API_KEY, optionalOPENAI_API_KEY, user-readable files, network access, and any processes the account is permitted t ...[truncated 221 chars]- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed version. - Commit a lockfile containing resolved transitive dependency versions and integrity metadata.
- Verify npm package integrity and publisher provenance before execution.
- Disable or explicitly review package lifecycle scripts where practical.
- Prefer installing the package separately and invoking a verified local binary rather than combining retrieval and execution in one command.
- Publish the reviewed implementation with the Skill or link it to an immutable source revision.
- Run installation and setup under a dedicated, low-privilege account without access to unrelated credentials or production data.
- Establish an update process that audits each new package version before changing the pinned version.
- Replace
