ClawAudit verdict

openclaw-whatsapp

45
🟠 Risky
Significant concerns — only install if you understand the risks

Setup instructs running curl piped directly to bash from a GitHub repo owned by an unknown user, downloading and executing untrusted code with no integrity verification.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

0
security
70
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Findings (6)

Pattern match critical

Pipe-to-shell pattern (curl | sh) — supply chain attack vector

SKILL.md · code · curl -fsSL https://raw.githubusercontent.com/0xs4m1337/openclaw-whatsapp/main/in

Pattern match critical

Pipe to bash — executes piped content as shell commands

SKILL.md · code · | bash

Pattern match high

References sudo — requests elevated privileges

SKILL.md · code · sudo

Pattern match high

Pipe-to-python pattern — remote code execution risk

scripts/wa-notify-worker.sh · prose · downgraded · curl -s "http://localhost:8555/chats/${jid}/messages?limit=10" | python

Pattern match high

Pipe to python — executes piped content as Python code

scripts/wa-notify-worker.sh · prose · downgraded · | python3

Pattern match low

References webhook/callback URL

references/api-reference.md · prose · downgraded · webhook_url

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class A/B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

network_out

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API