raptor-dex

SUSPICIOUS / high-risk vulnerable skill. Its stated crypto-trading purpose matches the blockchain capabilities, but the trust model is weak because the skill asks the agent/user to clone and execute a bundled binary plus signature file, then pass service tokens into it. The data flows are broadly coherent for a DEX aggregator, yet the binary is a black box handling credentials and transaction submission, so risk is high even without proof of malicious intent.

No direct indicators of embedded malware (no credential theft/exfiltration, no obfuscation for malicious execution, no subprocess/file manipulation). The main security concern is a high-impact trust/integrity boundary: the script signs a transaction constructed entirely by a remote service without local validation that it matches the requested swap parameters. Compromise or MITM of RAPTOR_URL (notably with the default HTTP scheme) could cause the user to sign and submit harmful transactions. Treat RAPTOR_URL as highly sensitive; implement HTTPS/pinning and add local transaction content validation (instruction/program/mint/amount checks) before signing if you intend to use this safely in adversarial settings.