Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Apex
v1.0.0Trade and monitor ApeX perpetual futures. Check balances, view positions with P&L, place/cancel orders, execute market trades, or submit trade reward enrollm...
⭐ 0· 38·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description and the included scripts (apex.mjs, analyze-market.mjs, etc.) are coherent with an ApeX trading/monitoring skill. However the package requires API keys and an Omni seed for private operations while the registry metadata lists no required environment variables — an inconsistency that may confuse users and lead them to unknowingly supply sensitive secrets.
Instruction Scope
SKILL.md clearly limits runtime actions to market data queries, account queries, and order operations via the Apex SDK and CoinGecko. It instructs interactive confirmations before trade execution and explicitly warns not to share the Omni seed. The scripts read/write a local trading-state.json inside the skill and call only the listed APIs; there are no obvious commands that read unrelated system files or exfiltrate data to unexpected endpoints.
Install Mechanism
There is no formal install spec, but SKILL.md instructs users to run npm install in the scripts folder. That will pull multiple npm packages including an 'apexomni-connector-node' package at version 0.3.2-alpha.1 (an alpha release). Installing packages from npm (especially an alpha/unreviewed connector) increases risk compared to an instruction-only skill — review the connector package source before installing.
Credentials
The runtime requires highly sensitive secrets (APEX_API_KEY, APEX_API_SECRET, APEX_API_PASSPHRASE, APEX_OMNI_SEED). Those are appropriate for trading functionality, but the registry metadata does not declare them (required env vars: none, primary credential: none). The omission is a significant transparency problem: users may not realize they must provide private keys/seeds when enabling the skill.
Persistence & Privilege
The skill does not request elevated platform privileges or always: true. It writes a local trading-state.json (in the skill folder) to persist last checks and positions — normal for a trading helper but worth noting because it stores account and position data locally. Autonomous invocation is allowed by default (disable-model-invocation: false), which combined with access to live trading credentials increases risk if the endpoint is misused.
What to consider before installing
This skill is functionally a trading client and needs full ApeX API credentials plus an Omni seed (used as a signing key). Before installing or running it: 1) Do not upload your real Omni seed or full-permission API keys to unknown services; keep them local. 2) Verify the source of the apexomni-connector-node package (check its repository/release page) — it is an alpha version in package.json and could be unreviewed. 3) Use API keys with restricted permissions (no withdrawal) and test first on testnet (APEX_TESTNET=1). 4) Inspect the connector package and skill code yourself (or have someone audit it) before running npm install. 5) Be aware the skill will write a trading-state.json file in the skill directory containing positions and account size; if that is sensitive, run in a sandboxed environment. 6) Because registry metadata does not declare the required env vars, expect manual configuration and treat that omission as a red flag — confirm credential handling and storage policies before trusting the skill to execute trades.Like a lobster shell, security has layers — review code before you run it.
latestvk97fr1feg0ttt97mwvzfawm2es84rc78openclawvk97fr1feg0ttt97mwvzfawm2es84rc78skillvk97fr1feg0ttt97mwvzfawm2es84rc78
License
MIT-0
Free to use, modify, and redistribute. No attribution required.