T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:15
- Finding
- Unpinned Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 15–20 **Vulnerability Type**: Unpinned and unverifiable third-party dependency **Risk Level**: Medium ```markdown ## Prerequisites The ActivityClaw plugin must be installed: ```bash npm install -g @rmruss2022/activityclaw openclaw plugins install @rmruss2022/activityclaw ``` ``` ### Technical Analysis The skill directs users to install `@rmruss2022/activityclaw` globally and as an OpenClaw plugin without specifying an immutable version or integrity digest. The project contains no lockfile, vendored source, checksum, or plugin implementation that would allow the installed artifact to be verified against the version reviewed during this audit. As a result, the effective package payload can change after the skill has been reviewed. If the package publisher account or distribution channel is compromised, a malicious release could be delivered under the same package name. npm lifecycle scripts may execute during installation with the privileges of the invoking user, while a loaded OpenClaw plugin may operate within the host application's trust boundary. The package name and repository reference are consistent, and no typographical dependency confusion or known malicious payload is demonstrated by the available file. The risk arises from mutable, unpinned supply-chain installation rather than confirmed malicious intent. ### Attack Path 1. An attacker compromises the package publisher account, npm package, or associated release process. 2. The attacker publishes a malicious release under the existing `@rmruss2022/activityclaw` package name. 3. A user follows the documented commands without pinning a previously reviewed version. 4. npm retrieves the attacker-controlled current release. 5. Malicious lifecycle code may execute during global installation, or attacker-controlled plugin logic may execute when OpenClaw loads the plugin. 6. The malicious package ab ...[truncated 854 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the dependency to a specific, reviewed version rather than installing the latest mutable release. 2. Verify the downloaded package with an approved integrity digest or signed provenance before installation. 3. Record the exact dependency version and integrity value in a lockfile or equivalent reproducible installation manifest. 4. Prefer project-local installation over global installation where supported to reduce the affected scope. 5. Review the package contents, lifecycle scripts, transitive dependencies, and OpenClaw plugin entry points before enabling it. 6. Disable npm lifecycle scripts during acquisition when compatible, then explicitly run only reviewed setup operations. 7. Execute the plugin under a least-privileged account and restrict access to sensitive files, credentials, network destinations, and message data. 8. Establish a controlled update process in which each new package version is reviewed and approved before deployment.