VirusTotal
6 / 91 engine detections
Open report“Stake EXTRA Tokens & Earn Rewards | ExtraFi”
6 / 91 engine detections
Open report1 threat-system alert
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | extrafi.digital |
malicious | Sinkholed |
PhishDestroy threat report
extrafi.digital posed as ExtraFi, presenting itself as the place to "Stake EXTRA Tokens & Earn Rewards." It targeted holders of the EXTRA token and DeFi users looking for staking yield. PhishDestroy first flagged it on 2026-09-02. The site has been offline since 2026-09-11, and its DNS was still inactive when we last checked on 2026-10-19.
A fake staking dashboard gives victims a reason to connect a wallet and approve transactions, because that is exactly what a real staking portal asks for. On a page like this, the "stake" or "claim rewards" button can trigger a token approval, a permit signature or a direct transfer instead of a deposit into ExtraFi's contracts. Once that is signed, the operator can move the approved tokens out of the wallet, and EXTRA is not the only asset at risk. The domain name and page title echo the real brand closely enough that a hurried user may not notice the different address.
Four blocklists list the domain: PhishDestroy, MetaMask, ScamSniffer and SEAL. This matters because MetaMask's list can trigger a warning inside the wallet itself. On VirusTotal, 6 of 91 engines flagged it on 2026-09-02: alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, Gridinsoft and Kaspersky. Most general-purpose scanners missed it, so the crypto-focused blocklists are the stronger signal here.
The domain was registered on 2026-05-15 through PDR Ltd. (PublicDomainRegistry.com), about 110 days before we detected it. That gap suggests it was held in reserve or ran quietly before drawing attention. The site sat behind Cloudflare (AS13335, US), which hides the real origin server. It used a free Let's Encrypt certificate, so the padlock in the browser said nothing about whether the site was legitimate.
If you connected a wallet to extrafi.digital, open a token-approval checker and revoke any allowances or permits you granted around the time of your visit. If you signed anything unfamiliar or tokens have already left your wallet, move your remaining funds to a fresh wallet. Treat any seed phrase you typed into the site as compromised. In the future, reach ExtraFi only through addresses you have verified independently. Defenders should block the domain and check wallet and DNS logs for connections made between 2026-09-02 and 2026-09-11.
Last checked
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.
Edge-IP reputation is not attributed to this domain.
amos.ns.cloudflare.comnola.ns.cloudflare.comLocation describes the IP network.
fa04af9532613ce8748deb9dccc8d08aef1a451351016baf53d33a10e59c4ce3Saved 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 extrafi.digital · checked Sep 2, 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.
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Reachable→Unavailable
Reachable
No threat flag
View sourcePD-20260902-7F88ED
6/91 engine detections
View sourceextrafi.digital
View sourcePage captured
View source79 stored lookalike domains
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
extrafi.digital
PD-20260902-7F88ED Recipient: abuse@publicdomainregistry.com Registrar: PublicDomainRegistry (PDR Ltd.) (India) Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
extrafi.digital)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.