VirusTotal
19 / 91 engine detections
रिपोर्ट खोलें“Account Recovery | Coinbase”
फ़िशिंग: walletrecovery.net — सामग्री अनुपलब्ध. साक्ष्य सारांश: VirusTotal 19/91 (alphaMountain.ai, BitDefender, CRDF, Ermes, ESET); URLQuery 2 det.; URLScan…
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
19 / 91 engine detections
रिपोर्ट खोलें2 det.
रिपोर्ट खोलेंदुर्भावनापूर्ण
रिपोर्ट खोलेंThreat flag recorded
रिपोर्ट खोलेंDBL_PHISH
दुर्भावनापूर्ण
रिपोर्ट खोलेंno community references
रिपोर्ट खोलेंResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
walletrecovery.net is a phishing page that impersonated Coinbase under the title "Account Recovery | Coinbase". It targeted Coinbase customers who believed they were locked out or needed to restore access. PhishDestroy first flagged it on 2026-09-23. The site has been offline since 2026-09-25 and was still dead when last checked on 2026-10-19.
Fake recovery pages exploit panic. A victim who thinks their account is compromised or frozen lands on what looks like an official Coinbase recovery flow. They are then asked for their email, password and two-factor codes, and sometimes a wallet recovery phrase, which the domain name itself hints at. Anything entered goes to the operators, who can log in, move funds out of the exchange account, or empty a self-custody wallet tied to a stolen phrase.
The classification is backed by several independent sources. VirusTotal shows 19 of 91 engines flagging the domain as of 2026-09-25, including BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, Emsisoft, alphaMountain.ai, CRDF and Ermes. Google Safe Browsing lists it for social engineering, urlscan.io rated it malicious and detected Coinbase branding, and Spamhaus DBL lists it as phishing. Besides PhishDestroy, the MetaMask and SEAL blocklists carry it, so many wallet users would have seen a warning.
The domain was registered through TUCOWS.COM, CO. on 2026-09-22, one day before PhishDestroy detected it. That gap points to a throwaway domain built for a short campaign. It was hosted on the Netiface LLC network, with the server located in Luxembourg, and served over a free Let's Encrypt certificate. The padlock in the browser therefore said nothing about whether the site was legitimate. The whole lifecycle from registration to going dark took about three days.
If you entered Coinbase credentials here, change your password at once from the official app and reset two-factor authentication. Review active sessions, connected devices and recent withdrawals, and contact Coinbase support through the app. If you typed a recovery phrase, treat that wallet as compromised and move any remaining funds to a new wallet with a fresh phrase immediately. Remember that Coinbase never asks for a seed phrase. Defenders should block the domain, hunt in mail and proxy logs for visits from 2026-09-22 onward, and watch for lookalike recovery-themed domains.
Last checked
1-you.njalla.no2-can.njalla.in3-get.njalla.foLocation describes the IP network.
cbc6ea5bdca45397e17b3c380bb80ef6a10b016a8b186a3439a217146ac0f41fSaved 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 walletrecovery.net · checked Sep 23, 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.
पहुँच योग्य→अनुपलब्ध
No flag recorded→Flag recorded
पहुँच योग्य
19/91 engine detections
View sourceThreat flag recorded
View sourcePD-20260923-04546B
Page captured
View sourcewalletrecovery.net
View source255 संग्रहीत मिलते-जुलते डोमेन
255 में से 100 दिखाए जा रहे हैं
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
walletrecovery.net
PD-20260923-04546B Recipient: domainabuse@tucows.com यदि आपने खाता क्रेडेंशियल, व्यक्तिगत या भुगतान जानकारी दर्ज की है, या इस डोमेन से कोई फ़ाइल डाउनलोड की है, तो तुरंत कार्रवाई करें। घटना की रिपोर्ट करने और अपनी सुरक्षा करने में आपकी सहायता के लिए नीचे संसाधन दिए गए हैं।
आधिकारिक साइबर अपराध संपर्क, या एक शिकायत ड्राफ्ट बनाएं → प्राप्त करने के लिए अपना देश चुनें।
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 ↗
walletrecovery.net)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
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
संग्रहीत ब्लॉकलिस्ट, WHOIS, DNS और सार्वजनिक स्कैन साक्ष्य का उपयोग करके खतरे का विश्लेषण
अभी स्कैन करेंसंदिग्ध डोमेन हमारे थ्रेट डेटाबेस में जमा करें — समुदाय की सुरक्षा करें
रिपोर्ट करेंहाल की फ़िशिंग रिपोर्टें और उपलब्धता में परिवर्तन देखे गए
निगरानी करेंलाइव खतरों की निगरानी करें या यदि आपको लगता है कि यह एक गलत सकारात्मक है तो इस लिस्टिंग को चुनौती दें।
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.