ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

okx-cex-bot

v1.2.8

Manage Grid bots (spot/contract/coin-margined) and DCA Martingale bots (Spot DCA 现货马丁 / Contract DCA 合约马丁) on OKX. Covers create, stop, amend, monitor P&L, T...

⭐ 0· 327·4 current·4 all-time
by@numpy0001
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
ℹ
Purpose & Capability
The SKILL.md clearly describes managing OKX Grid and DCA bots (create/stop/list/details) which matches the skill name and description. However, the runtime instructions require the OKX CLI (okx) and API credentials even though the registry metadata declared no required binaries or credentials — that's an inconsistency the author should justify.
ℹ
Instruction Scope
The instructions stay on-topic (running okx CLI commands, confirming profiles, not auto-transferring funds). They explicitly instruct checking/editing the user config at ~/.okx/config.toml and running okx config init, and they warn not to accept credentials in chat. Accessing the OKX config file is expected for a CLI-driven trading skill but is sensitive and should be disclosed in the registry metadata.
!
Install Mechanism
The SKILL.md frontmatter and README recommend installing @okx_ai/okx-trade-cli via npm (npm install -g ...). The skill package itself has no install spec in the registry, and there are no code files for review. Installing a globally scoped npm package has moderate risk (postinstall scripts, remote code). The registry should declare the install and provenance (npm package link, publisher) so users can verify the package on npmjs.org before running it.
!
Credentials
The runtime instructions state 'Requires API credentials' and instruct editing ~/.okx/config.toml, yet the registry shows no required env vars or primary credential. This omission understates the need for sensitive API keys and the file path the skill will use — the skill should declare required credentials and recommended permission scopes (e.g., bot/trade only, no withdrawals).
✓
Persistence & Privilege
The skill is instruction-only, has no code files, and is not always-enabled. It does not request persistent platform privileges. Normal autonomous invocation is permitted but not an additional risk here by itself.
What to consider before installing
Before installing or using this skill: (1) Confirm the skill author/publisher and verify the npm package @okx_ai/okx-trade-cli on npmjs.org and its maintainer — do not install blindly. (2) Demand that the skill registry metadata explicitly list required binaries (okx CLI) and required credentials, and explain recommended key scopes (use demo/read-only where possible). (3) Do not paste API secrets into chat; follow the skill's guidance to use okx config init or edit ~/.okx/config.toml locally. (4) Inspect the npm package (look for postinstall scripts) or run installation in an isolated environment (container/VM) first. (5) Prefer using a demo profile for testing and limit key permissions (no withdrawals). If the publisher cannot justify the missing metadata and provenance, treat the skill as untrusted.

Like a lobster shell, security has layers — review code before you run it.

latestvk977a9gvdp4abfb3bqt2jtw0m5845w29

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments