Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
haloeth.com favicon

haloeth.com

“编组 21”

Bureau d’enregistrement
TuringSign
Resolved IP
104.21.65.31
Registered
13/03/2026
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 11/91 Correspondances de la liste de blocage stockée : 2 Libellé de marque automatique : MetaMask
OTX: 5 refs 23/09/2026 CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 11. Listes de blocage publiques signalant une correspondance : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Résumé du rapport

Usurpation de MetaMask: haloeth.com — Dernier actif connu (HTTP 200). Résumé des preuves: VirusTotal 11/91 (alphaMountain.ai, BitDefender, Forcepoint…

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

Source evidenceVirusTotal 11 / 91 · OTX 5 references 5 sources

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

Analysis

Critique
VirusTotal
11 / 91
OTX
5 community refs
Page captures
2

PhishDestroy threat report

Overview

haloeth.com is an impersonation phishing page aimed at cryptocurrency users. Its name pairs "halo" with "eth", a pattern built to look like a legitimate Ethereum-related project or service. PhishDestroy first flagged it on 2026-09-23, and as of 2026-10-19 the site was still online and serving content.

How the scam works

Impersonation pages like this copy the look of a trusted crypto brand so visitors believe they are on the real service. They then push the victim to connect a wallet and sign transactions, or to type in a recovery phrase or private key. Either one can hand an attacker the funds in that wallet, and blockchain transfers cannot be reversed. The page title is "编组 21" (Chinese for "Group 21"), a generic design-layer label that names no brand, while we classify the site as impersonation phishing.

Evidence

MetaMask and SEAL list the domain independently, alongside PhishDestroy, which matters because those lists feed directly into wallet warnings. On VirusTotal, 11 of 91 engines flagged it as of 2026-10-01, including Kaspersky, BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, alphaMountain.ai and LevelBlue. Most engines still pass it, so a clean result from a single scanner should not reassure anyone. Five AlienVault OTX threat pulses also reference the domain.

Infrastructure

The domain was registered on 2026-03-13 through TuringSign Inc. d/b/a Cosmotown, about six months before we detected it. The long gap points to either a domain left idle before use or a site that ran for months without drawing attention. Traffic passes through Cloudflare, Inc., with the address placed in Canada, so the real origin server is hidden behind the proxy. Its Let's Encrypt certificate means the browser padlock reflects only encryption, not legitimacy.

What to do

If you connected a wallet to haloeth.com, revoke every token approval it was granted using a trusted allowance-checker, and move any remaining assets to a fresh wallet. If you entered a seed phrase or private key, treat that wallet as compromised and transfer everything out immediately from a clean device. Do not sign any further prompts from this site. Defenders should block the domain at DNS and proxy level, add it to mail and web filters, and report it to Cloudflare and Cosmotown for takedown.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-20T15:33:37Z

Observé: · Retrieved:

Uuid
01a0bf73-7063-75c7-a565-4a8a2d2dac7d
Final url
https://haloeth.com/
Statut
200
Ip
172.67.188.188
Contacted domains
[
    "ooudessd.oss-ap-southeast-1.aliyuncs.com",
    "plugin-code.salesmartly.com",
    "msg.salesmartly.com",
    "srz.salesmartly.com",
    "kf.dl237x.com",
    "api.salesmartly.com",
    "client.salesmartly.com",
    "assets-cdn.salesmartly.com",
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "47.79.48.159",
    "8.212.161.30",
    "104.18.22.242",
    "13.225.196.70",
    "104.18.23.242",
    "18.67.65.113",
    "104.16.80.73",
    "13.225.196.80",
    "172.67.188.188"
]
Asns
[
    "45102",
    "13335",
    "16509"
]
Countries
[
    "SG",
    "PH",
    "US"
]
Linked domains
[
    "www.salesmartly.com"
]
Document hash
ddf1d722a371a17130c8acef01f700ada14866688bfbc1dcc71cd58cae329f7b
Script hashes
[
    "cb0c6c9f1771d252eee7caa043bdd7cfffbd52c2cc4b18b7be7c4554ed069151",
    "13531f541bf1241f1aae77260bab6a2cd7fc33f3fb3e27c8a45fdb0e2c320c83",
    "d8f71c80480afd01e0e64e25a7d5bd8a5d9b85aee1b3fd5695623ea0e2598b5b",
    "58cf505f561e8516527a72d86606100c4961eb3879aab7d0fd96c70bdc169cfe",
    "16541e419322087b67e6e24b8f27aa3ef7575bbaa33ab2d2221aabf27f83f1bc",
    "74c9f93dc581cfe06132e0042c47f1d9b44f5d3ae02d39c4ba019bc5e9d15b04",
    "a1bf3191d9682f49110a3b77c0f02b5521571de0daf222dae2dd97f570f876f9"
]
Globals
[
    "TradingView",
    "addLink",
    "addMeta",
    "__ssc",
    "ssq",
    "install_ss_chat_plugin",
    "pluginInstall_ss_chat_plugin",
    "ssmEvent",
    "lib",
    "rem",
    "dpr",
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "__INTLIFY_PROD_DEVTOOLS__",
    "__INTLIFY_JIT_COMPILATION__",
    "__INTLIFY_DROP_MESSAGE_COMPILER__",
    "__VUE_I18N_FULL_INSTALL__",
    "__VUE_I18N_LEGACY_API__",
    "regeneratorRuntime",
    "PubSub",
    "__config",
    "__theme",
    "__VUE__",
    "__vite_is_modern_browser",
    "__cfBeacon",
    "chatwootSDK",
    "chatwootSettings",
    "$chatwoot"
]
Cookies
[
    "ss_uid",
    "_ss_s_uid"
]
Storage keys
[
    "salesmartly_p_gmvltt_session_tab_key",
    "salesmartly_p_gmvltt_u_i",
    "__storage_test__",
    "linc_THEME",
    "salesmartly_p_gmvltt_custom_fields_local_map",
    "salesmartly_p_gmvltt_p_xma_",
    "salesmartly_p_gmvltt_g_uid",
    "ss_p_c_l_v_pro",
    "salesmartly_p_gmvltt_token_date",
    "salesmartly_p_gmvltt_token",
    "salesmartly_p_gmvltt_n_u",
    "main",
    "linc_LANGUAGE"
]
Tls
{
    "san": [
        "*.haloeth.com",
        "haloeth.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "haloeth.com",
    "protocol": "QUIC",
    "valid_to": "2026-12-06T06:13:32Z",
    "valid_from": "2026-09-07T06:13:33Z"
}
Domain age days
190
Apex age days
190
Tls age days
13
Tls valid days
89
Requests
95
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 91,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-09-23T15:53:08Z

Observé: · Retrieved:

Uuid
4554d37c-0aaa-4011-bf91-678d00537925
Final url
https://haloeth.com/
Statut
200
History
[
    {
        "url": "https://haloeth.com/",
        "status": 200
    }
]
DOM structure hash
e864f7a127b72156c98b693d5e4a2b361a515c5263a9c47411cd0120c7f9aad4
Document hash
513d0308db1429ac063cf98d2ca02d44cbdd4b432c0c3aa770e00d3fa45b2375
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "haloeth.com",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "haloeth.com",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "haloeth.com",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    },
    {
        "name": "haloeth.com",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    }
]
Dnssec valid
false
Ip
188.114.96.0
Registration record
{
    "registrar": "TuringSign Inc. d/b/a Cosmotown",
    "created": "2026-03-13T20:33:34Z",
    "updated": "2026-03-13T20:46:02Z",
    "expires": "2027-03-13T20:33:34Z",
    "nameservers": [
        "nolan.ns.cloudflare.com",
        "ursula.ns.cloudflare.com"
    ]
}
Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Répertorié View source
PhishDestroy PhishDestroy list View source
SEAL Répertorié View source

Last checked

Capture enregistrée · 2 captures

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags crypto scamcrypto scamscyrptofraudinvestment fraudphishingscam
Bureau d’enregistrement TuringSign US(US)
Contact anti-abus["abuse@cosmotown.com"]
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 13/03/2026 (221d) — Expires 13/03/2027
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection23/09/2026
DOM Analysisanalyzed 09/10/2026score 100/100
Submitted URLhttp://haloeth.com/
Favicon Hash
Observed page title
编组 21
Certificat TLS
Émis par Let's Encrypt / YE1 · stored validity ends in 45 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.65.31
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

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

Serveurs de noms 1

  • ursula.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YE1
Valid from
2026-09-07 06:13:33
Valid until
2026-12-06 06:13:32
Validity
Within stored validity dates
Collection time
2026-10-11 04:03:25 UTC
Collection source
PhishDestroy collector
Certificate fingerprint35f2ca129389c5b36e8240c2bc927a29fa54e827a90617895bb32b369fa368a2

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-21 10:29:38 UTC

Primary outcome Contenu actif reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenu actif Ordinary HTTP content served 90% 2026-10-21 10:29:38 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-21 10:29:38 UTC last content: 2026-10-21 10:29:38 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

11 / Les fournisseurs de sécurité 91 ont signalé ce domaine
View on VT
Last analyzed Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
SOCRadar
Sophos

Preuves archivées

Wayback Machine Snapshot
Un instantané historique est disponible pour l’examen des preuves
View Archive
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of haloeth.com · checked Sep 23, 2026

55
Needs Work
Performance
FCP
6.69s
First Contentful Paint
LCP
9.2s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
117ms
Total Blocking Time
SI
13.5s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content 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.

haloeth.com
Résultat enregistré
Cloaked / Filtered
Stored observation history18

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→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

Earlier observations 13
  1. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  6. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  7. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  8. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  9. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  10. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  11. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  12. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  13. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    11/91 engine detections

    View source
  3. AlienVault OTX

    5 community references

    View source
  4. Added to PhishDestroy

    haloeth.com

    View source

Domaines ressemblants

79 domaines ressemblants enregistrés

Tout afficher (67)
metasmask.io insertion Rapport interne metramask.io insertion Rapport interne mewtamask.io insertion Rapport interne mmetamask.io homoglyph Rapport interne mtamask.io omission Rapport interne mwetamask.io insertion Rapport interne nmetamask.io homoglyph Rapport interne metamark.io bitsquatting Rapport interne metamaskj.io addition Rapport interne metammask.io homoglyph Rapport interne metamnask.io homoglyph Rapport interne emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

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é ?

4 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 haloeth.com)
  • 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/haloeth.com"
  title="PhishDestroy threat report for haloeth.com"
  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>