ClawAudit verdict
lead-contact-enrichment-agent
explorium-lead-enrichment
The skill transparently documents that search filters and entity IDs are sent to https://api.explorium.ai/v1/ for B2B data enrichment, which matches its stated purpose; credential access is limited to the EXPLORIUM_API_KEY for the service itself.
⚠ 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.
Permission integrity
file_read
Findings (4)
Possible hardcoded credential
setup.sh · prose · downgraded · API_KEY='$api_key
Accesses shell history/config
setup.sh · prose · downgraded · ~/.zshrc
Python urllib.request — network access
bin/agentsource.py · prose · downgraded · urllib.request
Python os.environ.get — reads environment variable
bin/agentsource.py · prose · downgraded · os.environ.get(
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class 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.
file_read Is this flag fair?
Thanks — recorded.