ClawAudit verdict
use-hln-api
The skill uses the Hyperliquid Names API for legitimate purposes such as name resolution, reverse resolution, and record lookups.
⚠ 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 (3)
Possible hardcoded credential
runner/run.sh · prose · downgraded · API_KEY="NILB2EY-R4LUDOA-WN5G5JQ-KHAQOLA
Instruction-prose smuggling shape detected: collects a sensitive target ("api_key") and emits it outward ("Send"). Phrased as prose with no trigger tokens — a semantic prompt-injection / data-exfil pattern the syntactic scanners can't see. Final tier capped at Caution; review the instructions before installing.
SKILL.md · Use these defaults unless the task says otherwise: - `base_url`: Default read-only requests to `https://api.hlnames.xyz/`. Use `https://api.testnet.hlnames.xyz/
Popular HTTP library — network access
evals/use-hln-api.lvl1.yaml · prose · downgraded · got
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.