ClawAudit verdict
obverse-payments
Stablecoin payment link creation skill using a user-registered OBVERSE_API_KEY to call the documented obverse.onrender.com API; all operations match the stated USDC payment processing purpose.
⚠ 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
network_out
Findings (7)
Possible hardcoded credential
SKILL.md · code · API_KEY="obv_sk_your_key_here
Pipe-to-shell pattern (curl | sh) — supply chain attack vector
DEPLOYMENT.md · code · curl -fsSL https://openclaw.ai/install.sh | bash
Pipe to bash — executes piped content as shell commands
DEPLOYMENT.md · code · | bash
Accesses OpenClaw config/secrets directly
README.md · code · ~/.openclaw/openclaw.json
References sudo — requests elevated privileges
README.md · code · sudo
apt-get install — installs system packages
README.md · code · apt-get install
Accesses sensitive environment variables
obverse-cli.js · prose · downgraded · process.env.OBVERSE_API_KEY
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class A). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
Requires 1 environment variable. (1 sensitive: OBVERSE_API_KEY).
network_outcredential_accessnetwork_in Is this flag fair?
Thanks — recorded.