T08 · Insecure Dependencies
- Location
scripts/publish-to-halo.sh:34- Finding
Unpinned Packages May Be Downloaded and Executed at Runtime
- Content
View full analysis
HTML if npx marked "$TMP_DIR/body.md" > "$TMP_DIR/body.html" 2>/dev/null; then HTML_MODE=true else echo "Warning: HTML conversion failed, falling back to Markdown import." HTML_MODE=false fi ``` The installation instructions similarly install the latest globally available Halo CLI release without a version or integrity constraint: ```bash npm install -g @halo-dev/cli ``` If `marked` is not already available locally, `npx` can resolve and download it from the configured npm registry before executing it. Consequently, the code that runs is not fully represented by the audited project and can change after review. A compromised package version, registry, lockless dependency chain, or npm configuration could execute arbitrary code with the privileges of the account running the skill. Redirecting standard error does not mitigate this risk; it only hides relevant installation or execution diagnostics. ### Attack Path 1. The operator invokes `publish-to-halo.sh` on a system where `marked` is not locally pinned and installed. 2. `npx` resolves `marked` using the current npm configuration and registry state. 3. An attacker compromises the resolved package, one of its dependencies, the configured registry, or the dependency resolution path. 4. The malicious package executes during the Markdown conversion step. 5. The payload inherits the publishing process's user privileges and may access the user's files, OpenClaw session data, Halo credentials, environment variables, and network connectivity. ### Impact Assessment Successful exploitation provides arb ...[truncated 428 chars]- Remediation
View remediation
