VirusTotal
13 / 92 engine detections
Ouvrir le rapport“Flare: The blockchain for data”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 10 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Hameçonnage: sitemv2bvw1q0rem.cfd — Non vérifié. Résumé des preuves: VirusTotal 13/92 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker)…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
13 / 92 engine detections
Ouvrir le rapport3 det.
Ouvrir le rapportMalveillant
Ouvrir le rapportMalveillant
Ouvrir le rapportno community references
Ouvrir le rapportNo threat flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
sitemv2bvw1q0rem.cfd is an impersonation phishing page that copies Flare Network and presents itself under the title "Flare: The blockchain for data". It targets Flare community members and anyone holding assets on the network who might land on what looks like an official Flare page. PhishDestroy first saw it on 2026-10-10. When last checked on 2026-10-19, the domain was still alive, but its DNS was no longer serving the phishing content.
The page borrows Flare's branding and tagline so a visitor believes they are on the project's real site, usually after following a link promising an airdrop, a reward claim or a wallet update. Fake pages like this then push the visitor to connect a wallet, sign a transaction or type in a recovery phrase. A signed approval lets the operator move tokens out of the wallet. A typed seed phrase hands over the entire wallet. In both cases the loss is immediate, and on-chain transfers cannot be reversed.
On 2026-10-14, 13 of 92 VirusTotal engines flagged the domain, including alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Kaspersky. Those are mostly established security vendors rather than a single fringe feed. urlscan.io rated the page malicious and identified the brand it imitates as flarenetwork. The domain also appears on wallet-focused blocklists from MetaMask, ScamSniffer and SEAL, as well as PhishDestroy's own list. That means many wallet users would already see a warning before connecting.
The domain was registered through Spaceship, Inc. on 2026-10-10, the same day PhishDestroy detected it. That pattern fits a throwaway domain set up for a short campaign. The random-looking name on a cheap .cfd extension has no connection to Flare at all, so it relies entirely on the page's look to fool visitors. It sits behind Cloudflare, Inc. on an address geolocated to Canada, which hides the real origin server.
If you connected a wallet to this site, use a token-approval checker to revoke any permissions you granted, and move remaining funds to a fresh wallet. If you entered a recovery phrase, treat that wallet as fully compromised and transfer everything you can to a new wallet with a new seed right away. Only reach Flare through bookmarks or links from its verified official channels, never through airdrop or claim links. Defenders should block the domain at DNS and proxy level and add it to wallet and mail filtering. They should also report any new random-string .cfd domains that carry Flare branding.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/FlareNetworkStored page referenceIoC extraction recorded 2026-10-11 04:01:40 UTC
Last checked
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
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.
La réputation Edge-IP n’est pas attribuée à ce domaine.
bradley.ns.cloudflare.comtreasure.ns.cloudflare.comLocation describes the IP network.
fdbed9a90221c2165e68010c444d794a237a099f652f0473d0e2a2481e31a13bSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of sitemv2bvw1q0rem.cfd · checked Oct 10, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Accessible
No threat flag
View source13/92 engine detections
View sourcePD-20261010-FCADF9
Page captured
View sourcesitemv2bvw1q0rem.cfd
View source52 domaines ressemblants enregistrés
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
sitemv2bvw1q0rem.cfd
PD-20261010-FCADF9 Recipient: abuse@spaceship.com 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.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
sitemv2bvw1q0rem.cfd)Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.