Skip to security report
Analytics Dashboard
Domain security report
blog.pancake.run favicon

blog.pancake.run

“Blog | PancakeSwap”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 12/89 Automated brand label: PancakeSwap
Sep 3, 2026 PancakeSwap CDN
API
Registrar
Tucows
Resolved IP
76.76.21.98
Registered
Feb 16, 2022
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 12. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
12 det.
CF Radar
Malicious
URLScan
URLScan
Report ↗
TLS Certificate
Hostname mismatch
Let's Encrypt · Certificate hostname mismatch
Age
4.7 yr
Observed status
Last known active 200
PhishDestroy
DestroyList
Listed

Source evidence

7 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

12 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing
View full Cloudflare Radar report

Evidence Summary

Critical
VirusTotal
12/89
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

blog.pancake.run returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check for that date. The same evidence set places the domain's first observation on 2026-09-03, roughly four weeks earlier.

Recorded Evidence

The HTTP check on 2026-10-01 recorded status 200 for blog.pancake.run, while the first observation of the domain dates to 2026-09-03. A PageSpeed check on 2026-09-03 returned a performance score of 67, and an SSL scan on the same date identified the issuer as Let's Encrypt / YR1. VirusTotal, checked on 2026-09-11, reported 12 detections across 89 scanners, with observation time known recorded as false. The publisher-owned PhishDestroy catalogue listed the domain, and the blocklist check date was 2026-10-01.

Interpretation

The PhishDestroy listing and the VirusTotal result come from different dates, so their counts and labels describe separate snapshots rather than one synchronized state. Because the HTTP, PageSpeed and SSL observations also fall on different dates, a reader can compare them only as dated records, not as a single current picture. The VirusTotal entry notes that observation time is not known, which limits how precisely that result can be aligned with the other dated checks.

Recommended Actions

Anyone reviewing blog.pancake.run should retain the dated records exactly as captured, including the HTTP, PageSpeed, SSL and VirusTotal entries, so later comparisons rest on the same source values. A follow-up check of blog.pancake.run should be compared against these dates rather than treated as a replacement for them. During any review, avoid submitting sensitive information to the domain until the recorded observations have been independently verified.

Data coverage & collection

20 · datasets with records / 11 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
12 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
maliciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Tucows Domains Inc.Collection time not recorded
Network & DNS
76.76.21.98 · 1 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
3 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
67/100 · mobile performance
Availability history
30 · stored state changes
Source observation history
5 · stored source events
Lookalike relationships
83 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 11

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.
Extracted from stored page analysis

Observed indicators

2 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0x3c2F61f2E27C865981D2e7aAf6b2CDf823030039Format validated · Domain analysis
ETH
0xB0f09ea9ae0515C3551080D4a745C8115aA30e37Format validated · Domain analysis
Telegram
https://t.me/leo0628Stored page reference

IoC extraction recorded 2026-09-03 04:00:05 UTC

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Tucows Domains Inc. · 76.76.21.98 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
Observed indicators2 wallet · 1 Telegram — full values ↗
IP Context Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Tucows CA(CA)
Abuse contactabuse@vercel.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for pancake.run →
Registration (base domain)pancake.run · Created Feb 16, 2022 — Expires Feb 16, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 3, 2026
DOM Analysisanalyzed Oct 9, 2026score 88/1001 brand signal
IoC Extractionscanned Sep 3, 20262 wallet · 1 Telegram IoCs
Submitted URLhttp://blog.pancake.run/
Favicon Hash
ICANN OVERSIGHT Registration: pancake.run

Accreditation and RAA context
Registrar accreditation and DNS abuse obligations

For the registrable domain pancake.run behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
76.76.21.98
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Nameservers 1
  • ns2.vercel-dns.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-07-30 01:09:49
Valid until
2026-10-28 01:09:48
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-03 01:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint0bdd49f37c8cf6900e62da42cdea4ac898567977e2e043f5761aa1f7782995c8
Certificate names · 1 SANs
  • pancake.run

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 76.76.21.98rapiddns.io

Latest Classified Outcome 2026-10-17 10:24:46 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-17 10:24:46 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 10:24:46 UTC last content: 2026-10-17 10:24:46 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 8 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 12 detections
ADMINUSLabs
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of blog.pancake.run · checked Sep 3, 2026

67
Needs Work
Performance
FCP
2.56s
First Contentful Paint
LCP
9.27s
Largest Contentful Paint
CLS
0.033
Cumulative Layout Shift
TBT
180ms
Total Blocking Time
SI
4.39s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
Vercel

Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=Vercel

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. VirusTotal Detections Update 2026-09-04 16:01:21 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 12 to 12. Added scanner alerts: Webroot. Resolved alerts: OpenPhish.
  2. VirusTotal Detections Update 2026-09-03 22:09:54 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 11 to 12. Added scanner alerts: Chong Lua Dao.
  3. VirusTotal Detections Update 2026-09-03 04:36:41 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 9 to 11. Added scanner alerts: Lionic, VIPRE.
  4. VirusTotal Detections Update 2026-09-03 01:21:58 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 11 to 9. Resolved alerts: Lionic, VIPRE.
  5. Threat First Observed 2026-09-03 00:50:45 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 76.76.21.98.
Stored observation history35

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 30
  1. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    protected→live_content

    content_served

  5. Availability monitor · Recorded state

    live_content→protected

    http_access_restricted · access_restriction

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  17. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  19. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  20. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  21. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  23. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  24. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  25. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  26. VirusTotal · Detection count

    12→12

  27. VirusTotal · Detection count

    11→12

  28. VirusTotal · Detection count

    9→11

  29. VirusTotal · Detection count

    11→9

  30. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Monitoring

13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
blog.pancake.run detected and queued for full analysis
Sep 3, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 3, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Sep 3, 2026
VirusTotal
12/89 recorded on VirusTotal
Sep 11, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Brand Impersonation
Impersonation of PancakeSwap
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Sep 3, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
VT Detection +1
+1 new detection (11 → 12): Chong Lua Dao
Sep 4, 2026
VT Detection +2
+2 new detections (9 → 11): Lionic, VIPRE
Sep 3, 2026
VT Detection -2
2 detections removed (11 → 9)
Sep 3, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 3, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Lookalike domains

83 stored lookalike domains

pancckeswap.finance bitsquatting Internal report lancakeswap.finance replacement oancakeswap.finance replacement p.ancakeswap.finance subdomain pabcakeswap.finance replacement pacnakeswap.finance transposition pahcakeswap.finance replacement panackeswap.finance transposition pancaekswap.finance transposition pancakeawap.finance replacement pancakedwap.finance replacement pancakeewap.finance replacement
Show all (71)
pancakes.wap.finance subdomain pancakesaap.finance replacement pancakesawp.finance transposition pancakeseap.finance replacement pancakeswal.finance replacement pancakeswao.finance replacement pancakeswap-finance.com various pancakeswapfinance.com various pancakeswpa.finance transposition pancakeswwp.finance replacement pancakeswzp.finance replacement pancakewsap.finance transposition pancakexwap.finance replacement pancakrswap.finance replacement pancaksswap.finance replacement pancakwswap.finance replacement pancameswap.finance replacement panckaeswap.finance transposition pancskeswap.finance replacement pancukeswap.finance vowel-swap pancwkeswap.finance replacement panczkeswap.finance replacement pandakeswap.finance replacement panfakeswap.finance replacement panxakeswap.finance replacement pnacakeswap.finance transposition psncakeswap.finance replacement puncakeswap.finance vowel-swap pwncakeswap.finance replacement pzncakeswap.finance replacement ancakeswap.finance omission paancakeswap.finance repetition pamcakeswap.finance homoglyph pancaakeswap.finance repetition pancaceswap.finance bitsquatting pancaieswap.finance bitsquatting pancajeswap.finance bitsquatting pancakdswap.finance bitsquatting pancakeeswap.finance insertion pancakesap.finance omission pancakesqap.finance replacement pancakessap.finance bitsquatting pancakesswap.finance insertion pancakesvvap.finance homoglyph pancakeswaap.finance insertion pancakeswapp.finance addition pancakeswapz.finance addition pancakeswaq.finance bitsquatting pancakeswp.finance omission pancakeswqp.finance bitsquatting pancakeswsp.finance replacement pancakeswwap.finance insertion pancakewap.finance omission pancakewwap.finance bitsquatting pancakgswap.finance bitsquatting pancakkeswap.finance repetition pancakswap.finance omission pancaoeswap.finance bitsquatting panccakeswap.finance repetition panckeswap.finance omission pancqkeswap.finance bitsquatting pankakeswap.finance bitsquatting panncakeswap.finance homoglyph panvakeswap.finance replacement pncakeswap.finance omission ppancakeswap.finance repetition pqncakeswap.finance bitsquatting qancakeswap.finance bitsquatting xn--pancakeswp-chb.finance homoglyph xn--pancakswap-wmb.finance homoglyph xn--pncakeswap-s4a.finance homoglyph

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 12 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including blog.pancake.run)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: blog.pancake.run

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Blog | PancakeSwap”. Apparent target: PancakeSwap.

VirusTotal detections for blog.pancake.run: 12 (2026-09-11 00:34:29 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/blog.pancake.run"
  title="PhishDestroy threat report for blog.pancake.run"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>