Sécurité des domaines et renseignements sur les menaces
pancakeswap.st
“Home | PancakeSwap”
Bureau d’enregistrement
ST Registry
Resolved IP
188.114.97.3
Registered
22/09/2026
Verdict de menace
Critique93/100
Disponibilité
Dernier actif connuDernière observation d'accessibilité stockéeObservé Source: HTTP probe
Signaux de risque
Détections VirusTotal : 1/89Correspondances de la liste de blocage stockée : 3Usurpation de l'identité de la marque : PancakeSwapDomaine jeune : 20 jours
Moteurs de sécurité signalant une détection : 1. Listes de blocage publiques signalant une correspondance : 3. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
Résumé du rapport
pancakeswap.st — Dernier actif connu (HTTP 200). Usurpation de l'identité de la marque : PancakeSwap; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 1/89 (CRDF); URLScan malicious verdict; 3 external blocklist matches (MetaMask, ScamSniffer, SEAL); CF Radar malicious; PhishDestroy score 93/100. Bureau d’enregistrement: ST Registry.
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
Stored evidence for pancakeswap.st: VirusTotal recorded 1 detections among 89 scanners on 2026-09-23. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for pancakeswap.st. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 1 detections among 89 scanners in the stored snapshot dated 2026-09-23. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-23 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for pancakeswap.st in the snapshot dated 2026-09-23. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains pancakeswap.st as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed pancakeswap.st on 2026-09-23. The MetaMask and SEAL blocklist snapshot is dated 2026-09-23 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-22. A URLScan reference was stored on 2026-09-23 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For pancakeswap.st, the registrar field records ST Registry; this is kept as an exact source value. The source stores 188.114.97.3 as the observed address in this record. The registration date for pancakeswap.st is recorded as 2026-09-22. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The pancakeswap.st record states that VirusTotal recorded 1 detections among 89 scanners on 2026-09-23. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-23. PhishDestroy remains a separate publisher catalogue entry in the stored record. For pancakeswap.st, the registrar field records ST Registry; this remains separate from the other source fields. The observed address field in this record contains 188.114.97.3. The supported conclusion is bounded to the exact stored observations for pancakeswap.st. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to pancakeswap.st during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain pancakeswap.st as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to pancakeswap.st. The stored record does not justify extending that rule to 188.114.97.3 or to other infrastructure records.
Extracted from stored page analysis
Observed indicators
6 wallet · 14 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Vérification du cloaking et de la répartition du trafic
Pas encore numériséAucune différence entre les robots d'indexation et les navigateurs n'a encore été constatée
Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.
Indicateur de camouflage enregistré
Pas encore numérisé
Dernier scan de camouflage
En-tête du serveur détecté par le scanner
nginx/1.22.1
Note relative à la numérisation:alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.22.1
Vérification en direct des empreintes digitales d'TDS
Sept empreintes Keitaro ainsi qu’une comparaison entre robot d’indexation et navigateur, générées par le scanner PhishDestroy lorsque ce panneau est ouvert.
Certificate hostname mismatch·
Émis par Let's Encrypt / YE2· stored validity ends in 71 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
La réputation Edge-IP n’est pas attribuée à ce domaine.
Serveurs de noms 2
clark.ns.cloudflare.com
ulla.ns.cloudflare.com
Location describes the IP network.
Certificat TLS
Issuer
Let's Encrypt / YE2
Valid from
2026-09-23 16:20:05
Valid until
2026-12-22 16:20:04
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 04:03:18 UTC
Collection source
PhishDestroy collector
Certificate fingerprint413ea1e66b14f79c5751a3851a80fff6b22c33fe7c78d979d0cdc7e095980475Certificate names · 1 SANs
www.pancakeswap.st
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationContenu actifOrdinary HTTP content served90%2026-10-11 22:08:56 UTC
RDAP registrationInconnu
Observed timelinelast reachable: 2026-10-11 22:08:56 UTClast content: 2026-10-11 22:08:56 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 · 4 identified
Google Tag Manager
Tag managers
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of pancakeswap.st· checked Sep 23, 2026
66
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
12.56s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
157ms
Total Blocking Time
SI
4.52s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
VirusTotal Detections Update2026-09-23 09:13:59 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: CRDF.
Threat First Observed2026-09-23 08:09:12 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.
Processus de réponse aux menaces Pipeline
Découverte
Analysis
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Menace détectée
pancakeswap.st détectés et mis en file d'attente en vue d'une analyse complète
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.
Le domaine reste accessible ou restreint en accès ; des contrôles futurs pourraient mettre à jour cette 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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
Dear Team,
We are writing to report a phishing website that copies the cryptocurrency exchange PancakeSwap in order to put its visitors' wallets in front of a page built to empty them. Searching for the exchange's name returns pancakeswap[.]st among ten results, in second place,
3 reports filed for pancakeswap.st (2 written by people) · category: Phishing · source checked
“Dear Team,
We are writing to report a phishing website that copies the cryptocurrency exchange PancakeSwap in order to put its visitors' wallets in front of a page built to empty them. Searching for the exchange's name returns pancakeswap[.]st among ten results, in second place, under the title "Home | PancakeSwap". The name was registered on 22 September 2026, the day before we examined it.
The page that opens is a straight copy of the exchange. It shows the PancakeSwap logo and the same top”
— reported by Anonymous on Sep 25, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
4 evidence signal groups linked0 reports recordedDernier actif connu
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification.En savoir plus sur la fraude liée aux aides à la reprise →
Signalez-le à vos autorités locales
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Annuaire de 97 pays
Template-based draft · optional AI wording assistance requires separate consent
Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
Infrastructure et rapports associés
Les relations stockées sont regroupées par attribut de correspondance exacte. Un fournisseur ou un registraire partagé ne prouve pas à lui seul la propriété commune.
Lien direct Partage un fichier d'enregistrement ou un kit de hameçonnage identique.
Signal auxiliaire Partage d'infrastructures ou de marque cible ; cela ne prouve pas qu'il s'agisse d'un seul et même opérateur.
Uniquement pour la découverte Répertorié à des fins de navigation ; aucun attribut commun avec cet hôte.
Carte des infrastructures · pancakeswap.st
Chaque ligne correspond à une raison pour laquelle un domaine est associé à cet hébergeur. La taille des nœuds indique les détections de VirusTotal et les nœuds en pointillés sont déjà hors ligne. Les listes complètes figurent ci-dessous.
Le contenu correspond8
Même hachage de favicon ou même titre de page que cet hébergeur.
Ces rapports renvoient à la même adresse IP périphérique partagée. Ils facilitent la découverte des rapports mais n'impliquent pas de propriété commune ni de serveur d'origine partagé.
Enregistrés auprès du même bureau d'enregistrement. Un bureau d'enregistrement dessert des millions de clients sans lien entre eux ; ce regroupement constitue donc simplement un constat et ne prouve pas l'existence d'un lien.
