ClawAudit verdict
zsxq-fetch
Knowledge community post fetcher using a user-provided session token to access content the user is already authorized to view; no exfiltration, data stays local.
⚠ 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.
Findings (4)
Possible hardcoded credential
SKILL.md · code · TOKEN="你的token值
Accesses OpenClaw config/secrets directly
README.md · prose · downgraded · ~/.openclaw/.env
Node http/https module — low-level network access
fetch_topics.js · prose · downgraded · require('https')
Accesses sensitive environment variables
fetch_topics.js · prose · downgraded · process.env.ZSXQ_TOKEN
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.
Is this flag fair?
Thanks — recorded.