Crypto Scam Checker | BTC + ETH Address | LegalAudit

Before you send to a wallet, paste it. The 30 seconds it takes are the cheapest insurance you'll ever buy. The Crypto Scam Checker queries multiple public reputation feeds (Chainabuse, CryptoScamDB, OFAC sanctions list, our own corpus of 388 documented scam patterns) and overlays live on-chain behaviour: how old is the wallet, what's its transaction velocity, has it sent funds to known mixer / tumbler clusters, has it received from previous-known-scam wallets.

We don't claim to know everything — fresh scam wallets created yesterday won't be in any database. But the pattern of 'address with zero history asking for $50,000 investment' or 'address that has received from 47 different victim wallets in the last 30 days' is detectable on-chain even before anyone reports it. That's the gap the Crypto Scam Checker covers: behaviour-based detection on top of static blacklists.

How it works

Paste the wallet address

Paste the BTC (P2PKH, P2SH, P2WPKH/Bech32, Taproot) or ETH (0x...) address into Mythos. ENS names also work — they're resolved server-side.

Tell Mythos the context

Mention how you got the address (investment platform, romance contact, recovery agent, etc.). Context drives which scam taxonomy to weight more heavily in the reputation lookup.

Read the reputation verdict

You get GREEN (clean across all feeds), AMBER (suspicious behaviour, no direct report yet), or RED (matched a known scam wallet). Each flag links to its source: OFAC ref number, Chainabuse report URL, our internal corpus entry.

Generate the dossier if you sent funds

If you already sent funds, the forensic dossier captures the wallet evidence with on-chain transaction hashes, makes the case for the bank's fraud team (under PSD2 / DSP3 your bank may be obligated to investigate), and provides the format complaint templates need for Polizia Postale, IC3, Action Fraud, etc.

What we detect

OFAC SDN list hits (US Treasury sanctions)

Chainabuse, CryptoScamDB, and BitcoinAbuse reports

Mixer / tumbler cluster proximity (Tornado Cash, Wasabi, Sinbad)

Pig butchering wallet topology (many small-victim inputs)

Rug pull contract patterns (mint authority retained, hidden tax)

Drainer signature patterns (Inferno, Pink, Angel Drainer families)

Wallet age vs. transaction velocity outliers

Cross-reference with LegalAudit 388-entry scam corpus

Token approval scam contracts (revoke.cash precursor signals)

DEX honeypot detection (sell function reverts for non-owners)

Frequently asked questions

Can you recover crypto I have already sent?

No service can guarantee crypto recovery — and any agency promising guaranteed recovery for an upfront fee is itself a scam (the well-documented 'recovery scam' / 'pig butchering recovery scam' pattern, corpus entry SW-RECOVERY-FEE). What we do is produce a forensic dossier that materially improves the chances of action by law enforcement, the destination exchange (KYC freeze requests), and your bank. Crypto sent to an exchange (Binance, Coinbase, Kraken) that has KYC on the receiving wallet can sometimes be frozen if the complaint reaches them within the first 24-72 hours.

Why does an old, clean-looking wallet still get flagged AMBER?

Because pig butchering wallets are often clean by design. The scammer rotates fresh wallets per victim cohort, so the wallet you see has no prior fraud reports — until the first victim files a complaint. The AMBER verdict flags behavioural anomalies: wallet age < 90 days, no outbound activity to legitimate counterparties, only victim-shaped inbound transactions (many similar amounts from many different wallets). It's a heuristic, not a confirmation, and we mark it as such.

What chains do you support?

Bitcoin (all address formats including Taproot), Ethereum and EVM-compatible chains (Polygon, BSC, Arbitrum, Optimism, Base, Avalanche C-Chain), plus Tron (USDT-TRC20 is heavily used in pig butchering). Solana support is in beta. For chains we don't yet index, the chat can still cross-reference reported addresses in our corpus, but live on-chain behaviour analysis won't run.