Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
hoomepage-ledger.zapier.app favicon

hoomepage-ledger.zapier.app

“Forms”

Bureau d’enregistrement
Name.com
Resolved IP
64.239.123.129
Registered
20/09/2022
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 15/89 Libellé de marque automatique : Ledger
06/09/2026 CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 15. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Résumé du rapport

Usurpation de Ledger: hoomepage-ledger.zapier.app — Dernier actif connu (HTTP 308). Résumé des preuves: VirusTotal 15/89 (Criminal IP, alphaMountain.ai…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 15 / 89 5 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critique
VirusTotal
15 / 89
Page captures
2

PhishDestroy threat report

Overview

hoomepage-ledger.zapier.app is a phishing page that impersonates Ledger, the hardware wallet maker, and targets people who keep crypto on Ledger devices. The misspelled "hoomepage" label is meant to pass at a glance as an official Ledger homepage. PhishDestroy first detected it on 2026-09-06. It was still alive when last checked on 2026-10-19.

How the scam works

The page carries the generic title "Forms" rather than any Ledger branding, but we classify it as Ledger impersonation phishing. Schemes like this typically tell the visitor that their device needs a sync, update or security check. They then ask the visitor to type the 24-word recovery phrase into a form. Anyone holding that phrase can rebuild the wallet on their own device and move every asset out, and the hardware wallet cannot block it. Ledger never asks for a recovery phrase through a website or form.

Evidence

When VirusTotal checked the domain on 2026-09-17, 15 of 89 security engines flagged it. They include ESET, BitDefender, Fortinet, CRDF, Criminal IP, alphaMountain.ai, CyRadar and Chong Lua Dao. That is a solid minority of independent vendors, which means many browsers and security tools will already warn users. Most engines still do not flag it, so some visitors will reach the page without any warning. PhishDestroy lists the domain on its blocklist.

Infrastructure

The page sits on a subdomain of zapier.app, a shared platform domain registered on 2022-09-20 through Name.com, Inc. That date belongs to the platform, not to this phishing page. The scammers borrowed an established, trusted parent domain instead of registering their own lookalike, which helps the page slip past filters that look for newly registered domains. Hosting resolves to Amazon.com, Inc. infrastructure in the US. The Let's Encrypt certificate only means the padlock appears and says nothing about legitimacy.

What to do

If you entered your Ledger recovery phrase on this page, treat the wallet as compromised. Set up a new device or a freshly generated seed and move any remaining funds to it right away, since the attacker can act at any moment. Never reuse the exposed phrase, and ignore any follow-up messages offering "recovery" help, which are often a second scam. Defenders should block the full subdomain, report it to Zapier for removal, and remind users that Ledger never requests seed phrases online.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 2 captures

Observed page title
Forms
Certificat TLS
Émis par Let's Encrypt / YR1 · stored validity ends in 30 days

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Vercel shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
Registrar (base domain) Name.com US(US)
Contact anti-abus["abuse@name.com"]
Registre de l'ICANNICANN Lookup (RDAP) →
Registration (base domain)zapier.app · Créé 20/09/2022 — Expires 20/09/2027
Statut HTTP308 Permanent Redirect
Détails techniquesProvenance & timestamps
Première détection06/09/2026
DOM Analysisanalyzed 09/10/2026score 88/100
Favicon Hash
ICANN OVERSIGHT Registration: zapier.app

Contexte de l’accréditation et du RAA

Registrar accreditation and DNS abuse obligations

For the registrable domain zapier.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
64.239.123.129
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 1

  • ns2.vercel-dns.com

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YR1
Valid from
2026-08-22 02:51:05
Valid until
2026-11-20 02:51:04
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:29 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta813a4e503b35535fb96a4c8df328eb445fdbba2e1686ddb446de1bec037f88f

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 10:06:19 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-20 10:06:19 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-20 10:06:19 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
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

15 / Les fournisseurs de sécurité 89 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 15 detections
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE
Webroot
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

hoomepage-ledger.zapier.app
Résultat enregistré
Cloaked / Filtered
Stored observation history21

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→protected

    http_access_restricted · access_restriction

  3. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

Earlier observations 16
  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Inconnu→protected

    http_access_restricted · access_restriction

  7. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  8. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Indisponible→Accessible

  12. Availability monitor · Recorded state

    Inconnu→inactive

    http_no_content

  13. Availability monitor · Recorded state

    Inconnu→inactive

    http_no_content

  14. Availability monitor · Recorded state

    Inconnu→inactive

    http_no_content

  15. Availability monitor · Recorded state

    Accessible→Indisponible

  16. Availability monitor · First collection record

    Accessible

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    15/89 engine detections

    View source
  3. Added to PhishDestroy

    hoomepage-ledger.zapier.app

    View source

Domaines ressemblants

151 domaines ressemblants enregistrés

Tout afficher (88)
eldger.com transposition kedger.com replacement kledger.com insertion l3dger.com replacement ldeger.com transposition ldger.com omission le.dger.com subdomain lecger.com replacement ledber.com replacement ledegr.com transposition leder.com omission ledg3r.com replacement ledge.com omission ledged.com replacement ledgedr.com insertion ledgee.com replacement ledgeer.com repetition ledgercom.com various ledget.com replacement ledgewr.com insertion ledgger.com repetition ledgir.com vowel-swap ledgor.com vowel-swap ledgr.com omission ledgre.com transposition ledgrer.com insertion ledgsr.com replacement ledgwer.com insertion ledgwr.com replacement ledher.com replacement ledhger.com insertion ledsger.com insertion ledtger.com insertion ledyer.com replacement ledzer.com replacement leedger.com insertion legder.com transposition leger.com omission lerdger.com insertion lerger.com replacement lesger.com replacement lewdger.com insertion lidger.com vowel-swap lledger.com repetition lodger.com vowel-swap lrdger.com replacement lsdger.com replacement oedger.com replacement pedger.com replacement pledger.com insertion dedger.com bitsquatting hedger.com bitsquatting iedger.com homoglyph l-edger.com hyphenation ladger.com bitsquatting lcdlger.com homoglyph lddger.com bitsquatting lebger.com homoglyph leclger.com homoglyph ledcer.com bitsquatting leddger.com insertion ledeer.com bitsquatting ledeger.com insertion ledfer.com bitsquatting ledg-er.com hyphenation ledgar.com bitsquatting ledger0.com addition ledger1.com addition ledger4.com addition ledger5.com addition ledger6.com addition ledgerb.com addition ledgerc.com addition ledgerf.com addition ledgeri.com addition ledgern.com addition ledgerq.com addition ledgerx.com addition ledges.com bitsquatting ledgez.com bitsquatting ledgur.com bitsquatting lediger.com homoglyph ledqer.com homoglyph leeger.com bitsquatting leelger.com homoglyph lefger.com bitsquatting letger.com bitsquatting ludger.com bitsquatting

100 affichés sur 151

Données factuelles et rapports externes

Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

3 evidence signal groups linked 0 stored notification records Dernier actif connu

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Official reporting routes

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
After a phishing incident

Recommandations et conseils à l'intention des victimes

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Que dois-je faire tout de suite ?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment hoomepage-ledger.zapier.app)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

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.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/hoomepage-ledger.zapier.app"
  title="PhishDestroy threat report for hoomepage-ledger.zapier.app"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>