Threat Death Pyramid
From a single suspicious URL at the tip — through every parser, scraper, ad-monitor, and the AI engine — down to a wide base of vendors, registrars, evidence stores, and the public ledger that records its death.
In short
The Threat Death Pyramid shows how PhishDestroy handles a suspicious domain: discovery through feed parsers, ad and search monitors, lookalike-domain checks, social sources and a Telegram bot; AI verification and investigation; checks and reports through public scanners, which are separate services rather than a partner network; abuse notices to registrars and hosts, with retests; and a public record.
Example walk-through: the case, domain names, timings, wallet amounts and counters inside this diagram are illustrative, not live data. Live figures are in the panel above.
Discovery Network
30+ ParsersCertStream · OpenPhish · URLhaus
Ads MonitorGoogle · Bing · DuckDuckGo
SEO ScrapersTop-100 wallet keywords
Domain Monitordnstwist · 92 brands
Social MentionsYouTube · X · Reddit · Discord
Community Bot@PhishDestroyBot · Telegram
got DM from "support" claiming I won airdrop — asks to connect wallet + sign tx
Surfaced URL
AI Verification
PhishDestroy AI
Multi-signal verification · false-positive guard · attribution model
- Verifying heuristics
- Capturing screenshots
- Validating metadata
Verdict
Signals
- Heuristics
- Screenshot diff
- VT consensus
- Wallet drainer
- WHOIS < 7d
- Cloaked geo
Active Investigation
Code AnalysisJS deobfuscation · drainer signature
Public Scan EvidenceIndependent scanners · archived results
Wallet Tracedrainer addr · on-chain analytics
Evidence CaptureWARC · screenshots · DOM snapshot
Evidence VaultPostgres · S3 · Merkle log
We use public scanners, reputation checks and reporting channels. These are separate services, not a synchronized partner network. For a specific domain, inspect its stored scans and outgoing report history.
Public Scans & Security Reports
GoogleSafe Browsing
GoogleWeb Risk API
MicrosoftSmartScreen
VirusTotalDetection feed
CloudflareRadar / 1.1.1.1
YandexSafe Browsing
URLScan.ioPublic scan
ESETWebGuard
BitdefenderThreat exchange
NortonSafe Web
SymantecSiteReview
AviraCloud detection
Avast / AVGWeb Shield
KasperskyOpenTIP
Dr.WebOnline scanner
NetcraftTakedown API
PhishTankVerified vote
APWG eCXBulk feed
PhishStatsOpen feed
Phish.ReportHosting abuse
SpamhausDBL feed
PolySwarmMarketplace
CheckPhishBolster scan
QutteraMalware scan
URLquerySandbox
Criminal IPAsset intel
CRDFThreat Center
ScamadviserTrust score
MyWOTWeb of Trust
Pressure Channels
Abuse Notifications
Registrar abuseRFC2142 · DKIM-signed
3 openHosting abuseARF + JSON
5 openICANN escalationCompliance ticket
AutoNameserver alertNS-level relay
2 openForensic Evidence
Evidence packagetar.gz · S3 · WORM
SealedPDF reportCourt-ready
BuiltScreenshotsHeadless · 2× DPR
StoredMetadata logNDJSON · Merkle
AppendPublic Channels
GitHubphishdestroy/db
PushedLive map/live · SSE
StreamedTwitter / X@phishdestroy
PostedTelegramt.me/phishdestroy
PostedMastodon@pd@infosec.exchange
PostedPublic APIapi.phishdestroy.io
LiveRe-detection
+6h retestSandbox replay
Active+12h retestGeo + UA matrix
Pending+24h retest2nd-wave abuse
QueuedAttribution graphKit · operator · cluster
LinkedDeath & Public Record
Example: domain made unavailable
DNS resolved → NXDOMAIN. Hosting suspended by registrar. Wallet flagged across all consumer browsers.
Public record sealed
Committed to phishdestroy/db. Operator + kit linked to attribution cluster. Pinned in shame leaderboard.