VirusTotal
3 / 89 engine detections
Apri il rapporto“Ledger — Sign In”
Phishing di credenziali: ledger-7h3.pages.dev — Contenuto non disponibile. Riepilogo delle prove: VirusTotal 3/89 (alphaMountain.ai, Ermes, Fortinet); 2…
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
3 / 89 engine detections
Apri il rapportono community references
Apri il rapportoprovider verdict: clean
Apri il rapportoNo threat flag
Apri il rapportoNo malicious flag
Apri il rapportoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ledger-7h3.pages.dev is a credential phishing page built to look like an official Ledger login, aimed at owners of Ledger hardware wallets. PhishDestroy first flagged it on 2026-09-01. The site went offline on 2026-09-13 and was still dead and unreachable when last checked on 2026-10-19.
The page presented itself as "Ledger — Sign In," a screen that feels routine to anyone who manages crypto through Ledger's software. Fake Ledger sign-in pages typically ask for an email and password and then push for the 24-word recovery phrase, often framed as an account check or device sync. Ledger never asks for a recovery phrase on any website. Anyone holding that phrase can rebuild the wallet on their own device and empty it, so the victim loses the funds themselves, not just a login.
Only 3 of 89 VirusTotal engines flagged the site as of 2026-09-13: alphaMountain.ai, Ermes and Fortinet. That is a thin vendor consensus, and a clean result from most scanners would not have meant the page was safe. The classification also rests on wallet-focused blocklists. MetaMask and the SEAL security alliance list the domain alongside PhishDestroy, so a visitor using MetaMask would likely have seen a warning.
The site ran as a project on Cloudflare Pages, a free static-hosting platform. The free subdomain let the operator borrow a trusted parent domain instead of registering a lookalike name. It was set up on 2026-07-27, about five weeks before PhishDestroy detected it. That gap suggests the page sat ready or circulated quietly before it drew attention. Hosting resolved to Cloudflare, Inc. in Canada. The Google Trust Services certificate is the platform's standard one, so the browser padlock said nothing about legitimacy.
If you typed a recovery phrase into this page, treat the wallet as compromised. Set up a new device or seed and move any remaining funds to the new addresses right away. Do not reuse the old phrase. If you entered an email and password, change that password everywhere you reused it and turn on app-based two-factor authentication. Watch that inbox for follow-up phishing that pretends to be Ledger support. Security teams should block the domain and add recovery-phrase prompts on hosting-platform subdomains to their phishing-awareness material. Free *.pages.dev projects are cheap to spin up again under new names.
Last checked
La reputazione Edge-IP non è attribuita a questo dominio.
Location describes the IP network.
f33925b0b602f5d161947a1adc6aba32b8b7a584f2caf5f8b9bff93dad220d72Saved 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 ledger-7h3.pages.dev · checked Sep 11, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ledger-7h3.pages.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Raggiungibile→Non disponibile
Raggiungibile
No threat flag
View source3/89 engine detections
View sourceledger-7h3.pages.dev
View source151 domini simili memorizzati
Visualizzati 100 di 151
Listed domains receive at least one abuse report; this entry has no retained notification history.
Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.
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 ↗
ledger-7h3.pages.dev)Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.
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
Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica
Scansiona oraSegnala i domini sospetti al nostro database delle minacce — proteggi la comunità
SegnalaSegnalazioni recenti di phishing e modifiche osservate della disponibilità
MonitoraControlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo
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.