ClawHub
Back to skill

Security audit

Upload Clawhub

Security checks across malware telemetry and agentic risk

Overview

This skill is openly for AI-assisted DeFi trading, but it gives an AI and an external npm package transaction authority with a private operator key on BSC mainnet.

Install only if you are comfortable with AI-assisted DeFi execution on BSC mainnet. Use a fresh operator wallet with minimal gas only, never an owner or main wallet, pin and review the npm package before giving it a key, require explicit confirmation for every transaction or configuration change, avoid raw calldata unless independently verified, and keep tight on-chain spending and receiver limits.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
- Immediately explain that this is the operator hot wallet for AI only.
- Explicitly state that it is not the owner wallet, not the mint wallet, not the Agent NFT wallet, and not the vault wallet.
- Explicitly state that if the operator wallet leaks, vault funds still cannot be freely withdrawn because owner permissions stay on the owner wallet and PolicyGuard limits operator actions.
- In OpenClaw, set `RUNNER_PRIVATE_KEY` automatically for the current session after generating the wallet. Do not ask the user to set the environment variable manually.

2. Verify gas:
- Ensure the operator wallet has a small BNB balance for gas.
Confidence
82% confidence
Finding
The skill directs the AI to automatically set RUNNER_PRIVATE_KEY for the current session instead of requiring an explicit user-managed secret handling step. Even though this is framed as convenience in OpenClaw, automatic secret ingestion and session configuration increases the chance of unintended key exposure, misuse, or execution with a sensitive credential without sufficiently explicit user control.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
2. Always call it the operator wallet or AI hot wallet.
3. Always explain the dual-wallet model the first time setup is discussed.
4. Always warn that the operator wallet must not be used to mint, subscribe to, or hold the Agent NFT.
5. Do not ask the user to manually set `RUNNER_PRIVATE_KEY` in OpenClaw; AI should do it.
6. After setup is complete and the user provides a token-id, run readiness checks automatically before asking the user what to do next.
7. When multiple listings are available, recommend one by default and explain why.
8. Prefer the structured `status.readiness` fields over ad-hoc prose when deciding the next user-facing instruction.
Confidence
78% confidence
Finding
This guidance reinforces automatic handling of RUNNER_PRIVATE_KEY by the AI and automatic readiness checks before asking the user what to do next. In a DeFi execution skill, reducing user involvement around secret activation and operational state transitions can normalize agent-led action flow and increase the risk of unintended transactions or secret misuse if the surrounding controls fail.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.