Back to skill

Security audit

Binance Dca

Security checks across malware telemetry and agentic risk

Overview

This is a transparent Binance DCA trading helper, but it can place real recurring crypto buy orders if configured with trading API keys.

Install only if you intentionally want an agent or scheduled job to access Binance and place spot buy orders. Use testnet first, create a dedicated key with withdrawals disabled and spot-only permissions, avoid margin/futures permissions, prefer a secret manager or protected environment over shell startup files, set small per-run amounts, and regularly review or disable any cron/OpenClaw jobs.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Rogue AgentSelf-Modification, Session Persistence
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Findings (5)

Lp3

Medium
Category
MCP Least Privilege
Confidence
95% confidence
Finding
The skill clearly instructs use of shell commands (`bash scripts/dca.sh ...`) while declaring no permissions. That creates a capability/permission mismatch that can cause users or orchestration systems to invoke shell execution without appropriate review or sandboxing, which is risky for a trading skill that can place live orders.

Vague Triggers

Medium
Confidence
84% confidence
Finding
The trigger scope is broad enough to match generic investment or accumulation requests, which can cause the skill to activate in contexts where the user did not intend to execute a crypto-trading workflow. In an agent environment, overbroad invocation increases the chance of unintended shell use or accidental trading assistance being surfaced opportunistically.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
**Limitations:**
- No alerts if it fails
- No confirmations
- Silent execution

### OpenClaw Cron (Recommended)
Confidence
91% confidence
Finding
No confirmation

Session Persistence

Medium
Category
Rogue Agent
Content
1. Log in to [binance.com](https://www.binance.com)
2. Go to **Account** → **API Management**
3. Create a new API key:
   - **Label:** `OpenClaw-DCA` (or similar)
   - **Restrictions:** Enable **Spot & Margin Trading** only
   - **IP Whitelist:** Add your server IP for security (optional but recommended)
Confidence
78% confidence
Finding
Create a new API key: - **Label:** `OpenClaw-DCA` (or similar) - **Restrictions:** Enable **Spot & Margin Trading** only - **IP Whitelist:** Add your server IP for security (optional but reco

YARA rule 'backdoor_persistence': Backdoor persistence with malicious payloads (shell commands, SSH key injection, hidden root users) [malware]

High
Category
YARA Match
Content
**Make them permanent** (optional, add to `~/.bashrc` or `~/.zshrc`):

```bash
echo 'export BINANCE_API_KEY="your-api-key-here"' >> ~/.bashrc
echo 'export BINANCE_SECRET_KEY="your-secret-key-here"' >> ~/.bashrc
source ~/.bashrc
```
Confidence
89% confidence
Finding
echo 'export BINANCE_API_KEY="your-api-key-here"' >> ~/.bashrc; echo 'export BINANCE_SECRET_KEY="your-secret-key-here"' >> ~/.bashrc

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.