T08 · Insecure Dependencies
- Location
SKILL.md:48- Finding
Unverified Third-Party Code Is Downloaded and Executed During Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
ClawWall is a coherent outbound DLP skill, but its default network exposure and fail-open protection model need review before use.
Review before installing. Prefer binding the service to 127.0.0.1, set blockOnError to true if you rely on it for DLP, install in an isolated environment, and verify downloaded packages or source before running pip/npm build steps.
SKILL.md:48Unverified Third-Party Code Is Downloaded and Executed During Installation
SKILL.md:116Local Scanning Service Binds to All Network Interfaces by Default
SKILL.md:93Outbound DLP Enforcement Fails Open by Default
The documentation states that the skill does not make external connections and that plugin registration is manual, yet the installation flow explicitly uses pip, git clone, and npm install, all of which contact external package sources, and clawhub install clawwall installs the skill itself. For a manifest describing a local-only outbound DLP component, this overstates the operational isolation of the skill as delivered through the skill file.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X POST http://localhost:8642/api/v1/scan \
-H "Content-Type: application/json" \
-d '{"content": "key=AKIAIOSFODNN7EXAMPLE", "destination": "api.example.com"}'
The declared requirements include git, node, and npm, while the manifest frames the skill as a local Python service performing hard-regex scanning with no LLM. Those extra toolchain dependencies are only for fetching/building the optional OpenClaw plugin and are broader than the core DLP purpose suggests.
No suspicious patterns detected.