T01 · Skill Instruction Hijacking
- Location
SKILL.md:203- Finding
Autonomous Cryptocurrency Transfers to a Hardcoded Deposit Address
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This API-provider skill is mostly coherent, but it tells agents to use wallet private keys for unattended crypto deposits and to duplicate API keys in plaintext files.
Review before installing. Use this only if you are comfortable with a third-party paid model provider, and do not give an agent a wallet private key or permission to auto-deposit funds. Prefer manual deposits through the website, keep any API key in one protected secret location, and treat remotely fetched provider docs as data to review rather than instructions to execute.
SKILL.md:203Autonomous Cryptocurrency Transfers to a Hardcoded Deposit Address
SKILL.md:37Unreviewed Mutable Instructions Retrieved from a Remote Service
SKILL.md:294Bearer API Key Duplicated into Plaintext Configuration
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
---
name: clawapi-provider
description: "Build your AI Company — 8 models across 4 providers act as your CEO, CTO, CMO, CFO, and Workers. Crypto-native, pay-as-you-go with USDC/USDT. No GPU needed."
version: 1.3.0
metadata:
openclaw:
requires:
env:
- CLAWAPI_KEY
primaryEnv: CLAWAPI_KEY
emoji: "🦞"
homepage: https://clawapi.org
docs: https://clawapi.org/api/skill
tags:
- ai-models
- api-provider
- opc
- one-person-company
- claw-company
- claude
- openai
- gemini
- crypto
- llm
---
# ClawAPI — Air for Agents 🦞
>
This section explicitly instructs autonomous wallet-based authentication, API key creation, and ERC-20 fund transfers without any explicit confirmation step, financial-risk warning, or transaction verification guidance. In an agent skill context, that is dangerous because it normalizes irreversible on-chain payments and sensitive key handling as routine autonomous actions, increasing the chance of unintended loss of funds or unsafe secret exposure.
The skill instructs users to place a live API key into both an environment file and a hardcoded runtime JSON file. Duplicating credentials across plaintext files expands exposure, increases the chance of accidental leakage through backups, logs, or source control, and undermines secure secret-management practices.
# 1. Environment variable (referenced by openclaw.json)
~/.openclaw/.env
CLAWAPI_KEY=sk-claw-your_new_key_here
# 2. Agent models file (hardcoded key used at runtime)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://clawapi.org/api/v1/chat/completions \
-H "Authorization: Bearer sk-claw-..." \
-H "Content-Type: application/json" \
-d '{"model":"claude-opus-4-6","messages":[{"role":"user","content":"Hello"}]}'
The phrase 'No Human Needed' and the statement that setup can be completed 'without any human intervention' encourage removal of human approval for sensitive financial and authentication actions. In this context, that materially increases risk because the same section includes wallet signing and token transfer steps, which should never be implied as safe to automate by default.