aicoin-trading

Fail

Audited by Gen Agent Trust Hub on Sep 18, 2026

Risk Level: HIGHCREDENTIALS_UNSAFEREMOTE_CODE_EXECUTIONEXTERNAL_DOWNLOADSCOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTIONDATA_EXFILTRATION
Full Analysis
  • [CREDENTIALS_UNSAFE]: The file lib/defaults.json contains hardcoded accessKeyId and accessSecret for the AiCoin market data service. Hardcoding credentials in the skill source is a significant security risk.
  • [REMOTE_CODE_EXECUTION]: The script scripts/exchange.mjs includes logic in the getExchange function to dynamically install the ccxt package using npm install if it is not present in the environment. This allows for the execution of external code downloaded at runtime.
  • [EXTERNAL_DOWNLOADS]: The skill performs external downloads from the NPM registry during the dynamic installation of the ccxt library. It also contains several referral links to external exchange registration sites (e.g., jump.do).
  • [COMMAND_EXECUTION]: The scripts scripts/exchange.mjs, scripts/trade.mjs, and scripts/auto-trade.mjs utilize execSync and execFileSync to perform system-level operations, including package management and inter-script communication.
  • [INDIRECT_PROMPT_INJECTION]: As a tool for financial transactions, the skill is a target for indirect prompt injection via manipulated market data or user instructions.
  • Ingestion points: Natural language commands for trading spot and futures across various CEXs as defined in SKILL.md.
  • Boundary markers: Implements a strict two-step workflow (preview followed by a second call with confirmed: true) for all orders and configuration changes, providing a manual checkpoint.
  • Capability inventory: Capabilities include placing market/limit orders, setting leverage, managing stop-loss/take-profit, and handling CEX API keys.
  • Sanitization: Parameters are parsed into structured JSON objects and validated against exchange market data using the ccxt library.
  • [DATA_EXFILTRATION]: The skill accesses and modifies sensitive authentication files, specifically .env files located in the user's home directory (~/.coinos/.env) and other workspace paths, to manage exchange API keys.
Recommendations
  • AI detected serious security threats
Audit Metadata
Risk Level
HIGH
Analyzed
Sep 18, 2026, 12:45 PM