T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unpinned External npm Package Receives Global and Cloud-Capable Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19–28 and 40–49
Vulnerability Type: Unpinned third-party dependency and mutable supply-chain execution
Risk Level: HighVulnerable Code:
markdown This is the OpenClaw distribution of `dirextalk-deployer`. It is a thin bootstrap skill: the executable deployment engine must always come from the versioned npm package, not from a Git clone or this ClawHub bundle. Before deployment, repair, verification, update, or teardown, install the latest package: ```bash npm install -g dirextalk-deployer@latestUse the installed CLI to refresh the host-level skill when needed:
bash dirextalk-deployer skill refresh --agent openclawtext ```markdown Read the npm package's `SKILL.md` and `README.md` before acting. They define the required AWS billing confirmation, domain ownership confirmation, DNS handling, security boundaries, and exact lifecycle commands. The normal deployment entrypoint is: ```bash DOMAIN=<domain> bash scripts/orchestrate.shRun it only from the installed deployer skill/runtime directory after the required confirmations. Use its
status,verify,update, anddestroycommands for existing services.text ### Technical Analysis The audited skill contains no local deployment implementation. Instead, it directs the user or agent to globally install `dirextalk-deployer@latest`, making a mutable external npm release the effective executable payload. The package version is not pinned, and the project provides no lockfile, integrity hash, provenance requirement, or locally reviewable copy of the executed scripts. The installed package is also permitted to refresh the host-level OpenClaw skill and provide authoritative operational instructions through its own `SKILL.md` and `README.md`. Its orchestration script is expected to run in an AWS deployment context. Therefore, the behavior ultimatel ...[truncated 1955 chars]- Remediation
View remediation
Remediation Suggestions
- Replace
dirextalk-deployer@latestwith an exact, reviewed package version. Do not use a floating tag for security-sensitive deployment tooling. - Record and verify the expected package integrity digest and npm provenance before installation.
- Include or vendor the exact
SKILL.md,README.md, lifecycle scripts, package manifest, and lockfile that have been reviewed so the authorized behavior is visible in the audited artifact. - Prefer a project-local, isolated installation over a global npm installation. Disable npm lifecycle scripts during installation unless they are explicitly required and reviewed.
- Require explicit review and confirmation before executing skill refresh, deployment, update, or destruction operations.
- Run the deployer with a dedicated least-privilege AWS identity. Separate deployment, verification, update, and destruction permissions where practical.
- Execute the package in an isolated environment with restricted filesystem, network, and credential access.
- Pin updates through a controlled release process that reviews source changes, dependency changes, signatures, and integrity metadata before changing the approved version.
- Replace
