moltrade
WarnAudited by ClawScan on May 10, 2026.
Overview
This skill is openly about trading, but it asks users to run external, unreviewed trading code with exchange credentials and includes broad live Binance order controls.
Install only if you are comfortable reviewing and running the external Moltrade code yourself. Start with testnet or test mode, use dedicated API keys with no withdrawal permission, enable IP allowlisting where possible, confirm every live order/cancel/post action, and understand how Nostr signals and Square posts will share information externally.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
You could end up running code that was not included in this review while giving it access to trading accounts or keys.
The reviewed package is instruction-only, but it directs the user to fetch and run external code and dependencies. Because that external code is the trading runtime, it would likely handle credentials and order placement outside the reviewed artifacts.
git clone https://github.com/hetu-project/moltrade.git ... cd moltrade/trader && pip install -r requirements.txt
Before using live funds, inspect the GitHub repository and dependency list, pin a known commit, use a virtual environment, start on testnet/test mode, and avoid granting withdrawal permissions.
If used with mainnet credentials, an agent could place or cancel real Binance Spot orders and affect your funds.
The included Binance Spot skill exposes direct authenticated trading operations, including creating new orders and cancelling all open orders. These are high-impact account mutations and the visible raw API reference does not show strict confirmation, sizing, or mainnet safeguards.
`/api/v3/openOrders` (DELETE) | Cancel All Open Orders on a Symbol ... `/api/v3/order` (POST) | New order ... Authentication | Yes
Require explicit user confirmation for every live order or cancellation, use Binance testnet first, enforce order-size/risk limits, and restrict API keys to only the permissions needed.
Providing the wrong type of API key could let the bot or agent perform real trading actions on your exchange account.
The skill requires high-impact exchange credentials that can authorize account access and trading on mainnet. This sensitive credential requirement is not reflected in the registry's declared credential requirements.
Authentication requires API key and secret key. Supports testnet and mainnet.
Use separate testnet credentials first, create a dedicated API key with no withdrawal permission, enable IP allowlisting if possible, and do not paste secrets into chat unless you understand how OpenClaw stores them.
Your trading signals, strategy activity, or execution reports may be shared through configured relays.
The skill intentionally sends trading signals and execution reports through Nostr relays. This is purpose-aligned, but it involves external communication of trading activity and use of a Nostr private key.
Broadcast Signals to Nostr ... Check `nostr` block: `nsec`, `relayer_nostr_pubkey`, `relays`, `sid` ... verify `send_trade_signal` / `send_execution_report`
Verify the relay list, encryption behavior, recipient keys, and whether execution reports are necessary before enabling broadcasting.
A post could be published publicly under your Binance Square identity if you approve the posting flow.
The Square posting sub-skill can publish public Binance Square content when triggered. The artifact also says it should show optimized content and ask the user to choose, so this is disclosed, but it still affects a public account.
Auto-run on messages like 'post to square', 'square post'. Supports pure text posts.
Review the final text and account before posting, keep the Square API key narrowly scoped, and avoid granting trading or withdrawal permissions to a posting key.