crypto-scam-detector

What This Skill Does

The Crypto Scam Detector v2.0 is a robust, database-first security agent designed for OpenClaw. Unlike standard security tools that rely on sluggish third-party API calls at the moment of verification, this skill utilizes a high-performance local SQLite database. By decoupling the scanning process from the Etherscan API via a dedicated background sync worker, it ensures that your security checks are near-instantaneous (under 5ms). It proactively identifies threats including phishing attempts, honeypots, rug pulls, ponzi schemes, and sophisticated exploit recruitment messages. By analyzing hex data and transaction messages, it provides a deep-layer audit of suspicious addresses, protecting your assets without compromising on speed or connectivity constraints.

Installation

To integrate the Crypto Scam Detector into your workspace, ensure you have the OpenClaw environment active. Navigate to your workspace directory and use the clawhub installation command: clawhub install openclaw/skills/skills/princedoss77/crypto-scam-detector. After cloning the repository, execute the ./install.sh script to set up your virtual environment and dependencies. For optimal performance, run the ./setup.sh utility to securely encrypt your Etherscan API key, which will be utilized exclusively by the background sync worker to keep your local database updated with the latest threat intelligence.

Use Cases

• Proactive Wallet Protection: Quickly screen unknown transaction addresses before interacting with a decentralized application.
• Transaction Auditing: Analyze suspicious transaction history or hex-encoded data for hidden exploit signatures or malicious smart contract interactions.
• Asset Safety Monitoring: Maintain a local "blocklist" of known malicious actors like the Lazarus Vanguard group or Orbit Bridge hackers without triggering rate limits during active browsing or trading sessions.

Example Prompts

1. "OpenClaw, scan this address 0x71C7656... to see if it is flagged as a potential rug pull or honeypot in our local database."
2. "Check the transaction data associated with this hex input and tell me if it contains any known phishing or exploit keywords."
3. "Is this address associated with any known hacking groups like the Lazarus Vanguard or known private key theft campaigns?"

Tips & Limitations

• Sync Frequency: While the check is instant, ensure your sync_worker.py is running on a cron schedule to keep your database current with the latest threats.
• Zero API Latency: Because checks are local, the reliability depends on your local database being populated. If an address is brand new and not yet synced, consider adding it to the queue manually.
• Security: The skill uses encrypted storage for API keys; ensure you do not commit your .env or decrypted key files to any public repositories.