feat(feeds): ScamSniffer community scam-address feed#158
Merged
Conversation
#3 of the free on-chain roadmap. ScamSniffer's openly-published blacklist of crypto scam/phishing/drainer addresses (~2.5k EVM) — active-fraud coverage alongside OFAC's sanctioned set, hardening on-chain attribution without paying Arkham. Where OFAC is legal ground-truth, ScamSniffer is the scam wallets analysts actually hit. Plain JSON fetch (no deps), dual-sink mirroring ofac.ts: - iocs — type `crypto-address`, tagged `scam` → Landscape shift band. - wallets — entityType `scam`, attributionSource `scamsniffer`, confidence 75 (community intel, not authoritative like OFAC's 100). The wallet upsert is confidence-preserving: a scam label (75) never clobbers a higher-confidence attribution (OFAC sanctioned=100, or an analyst's manual one) — GREATEST(confidence) + CASE-guarded fields — so OFAC always wins regardless of feed run order. Registered as `scamsniffer`; daily 03:30 UTC. No migration (reuses iocs + wallets). Verified live against local DB: 2530 addresses → 2530 iocs + 2530 wallets, 0 failed; gateway tsc + api tests (16-feed registry) green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
#3 of the free on-chain roadmap: ScamSniffer's openly-published blacklist of crypto scam/phishing/drainer addresses (~2.5k EVM). Active-fraud coverage alongside OFAC's sanctioned set — together they harden the on-chain attribution layer without paying Arkham. Where OFAC is legal ground-truth, ScamSniffer is the scam wallets analysts actually hit.
Source
https://raw.githubusercontent.com/scamsniffer/scam-database/main/blacklist/address.json— a flat JSON array, no key, ~2530 lowercase0xaddresses. Plainfetch(no new deps, unlike OFAC's XML or AID's pagination).Dual sink (mirrors
ofac.ts)iocstype=crypto-address, tags[scam, scamsniffer, phishing, eth], confidence 75walletsentityType=scam,attributionSource=scamsniffer, confidence 75/onchainattributionCommunity intel → confidence 75 (vs OFAC's 100),
entity_type=scam(vssanctioned).Confidence-preserving wallet upsert
The wallet
onConflictDoUpdateusesGREATEST(confidence, excluded.confidence)+ CASE-guarded label fields, so a scam label (75) never clobbers a higher-confidence attribution — an OFAC sanctioned wallet (100) or an analyst's manual label survives. OFAC always wins regardless of feed run order.Verification (boundary-tested live)
Ran the connector against a local DB: 2530 addresses → 2530 iocs + 2530 wallets, 0 failed. Gateway
tsc(strict gate) + api tests (16-feed registry) green. No migration (reusesiocs+wallets).Registered as
scamsniffer; scheduled daily 03:30 UTC (30 min after OFAC).🤖 Generated with Claude Code