Aller au rapport de sécurité
Tableau de bord analytique
Sécurité des domaines et renseignements sur les menaces
breezeclient.com favicon

breezeclient.com

“Breeze Client — Free Cracked Minecraft Utility Client”

Bureau d’enregistrement
Web Commerce Communica…
Resolved IP
196.251.107.204
Registered
19/04/2026
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Signaux de risque
Détections VirusTotal : 14/91 Spamhaus DBL: DBL_PHISH Type d'arnaque : Impersonation
OTX: 9 refs 29/09/2026 1 Report Sent
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 14. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is compliance_abuse@webnic.cc. The latest stored availability evidence still shows the domain reachable; 21 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
21 days
Reports sent
1
Latest case ID
PD-20260929-BEFFFB
Current status
HTTP 200 at latest stored check
VirusTotal
14 / 91
engine detections
Google Safe Browsing
No threat flag
URLQuery
2
detections
OTX
9
community references
Page captures
3
open gallery
Domain age
183 days
Reports sent
1
view timeline
Résumé du rapport

Hameçonnage: breezeclient.com — Dernier actif connu (HTTP 200). Résumé des preuves: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, Forcepoint…

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

Source evidenceVirusTotal 14 / 91 · OTX 9 references 7 sources

Spamhaus DBL

DBL_PHISH

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

Renseignements sur la sécurité réseau
CF Cloudflare Radar Verdict Malveillant
Malware Malware Security threats
View full Cloudflare Radar report

Analysis

Critique
VirusTotal
14 / 91
OTX
9 community refs
Page captures
3
Page captures Source results Registration record

PhishDestroy threat report

Overview

breezeclient.com presents itself as "Breeze Client — Free Cracked Minecraft Utility Client" and imitates the Breeze Client brand. It is aimed at Minecraft players looking for free, unlicensed hacked or utility clients. PhishDestroy first detected it on 2026-09-29 and classifies it as an impersonation phishing page. As of 2026-10-19 the site was still online and serving its content.

How the scam works

The page title advertises a cracked utility client, which is software a player would normally get from the real project. We classified the domain as impersonation phishing rather than a genuine download portal. Fake game-client sites like this usually work in one of two ways. Some ask visitors to sign in with a game, launcher or community account, and those credentials go straight to the operators. Others push a download that can carry info-stealing malware, which harvests saved browser passwords, session cookies and crypto wallet files from the player's computer. In either case the victim can lose game and email accounts and, if wallets are on the same machine, funds.

Evidence

On 2026-10-01, 14 of 91 VirusTotal engines flagged the domain. The vendors include alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. Several major endpoint and web-filtering vendors agree on this, so many users with security software will already see a warning. Spamhaus lists the domain in its DBL with a phishing tag, and it appears in 9 AlienVault OTX threat pulses. The PhishDestroy blocklist also carries it.

Infrastructure

The domain was registered on 2026-04-19 through Web Commerce Communications Limited (WebNic.cc), more than five months before PhishDestroy flagged it. That long gap suggests the site was set up well in advance and may have run unnoticed for a while. It is hosted on the FEMO IT SOLUTIONS LIMITED network in Germany. Its Let's Encrypt certificate gives it a browser padlock, which proves nothing about who runs the site.

What to do

If you downloaded and ran anything from this site, disconnect the machine and run a full scan with up-to-date security software. Reinstalling the system is the safest option. Then, from a clean device, change the passwords for your Minecraft, launcher, email and Discord accounts, sign out of all active sessions and turn on two-factor authentication. If you keep a crypto wallet on the affected computer, assume its seed phrase is exposed and move the funds to a new wallet created on a clean device. Defenders should block the domain and its hosting IP, check endpoint logs for downloads from it, and report the impersonation to the legitimate Breeze Client maintainers.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded2026-09-29 09:25 UTC
StateStored capture
Position1 / 3
Open capture Wayback Télécharger

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
Réputation de l’IP abuse score 0/100 0 reports checked 29/09/2026
OTX tags 144-172-117-212144-172-84-8158-94-211-116172-86-123-51172-86-74-220172-86-84-161176-65-139-139176-65-139-145176-65-139-152176-65-139-153176-65-139-197176-65-139-208176-65-139-214176-65-139-217+6 more
Bureau d’enregistrement Web Commerce Communica… (Unknown)
Contact anti-abuscompliance_abuse@webnic.cc
Registre de l'ICANNICANN Lookup (RDAP) →
Recherche WHOISICANN RDAP pour breezeclient.com →
EnregistrementCréé 19/04/2026 (183d) — Expires 19/04/2027
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection29/09/2026
DOM Analysisanalyzed 09/10/2026score 98/1002 brand signals
Submitted URLhttps://breezeclient.com/
Favicon Hash
ID du dossier
Observed page title
Breeze Client — Free Cracked Minecraft Utility Client
Automated brand references
Across Minecraft
Certificat TLS
Émis par Let's Encrypt / YR2 · stored validity ends in 60 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
196.251.107.204
Network ASN
AS214351
Organization
Femo IT Solutions Limited
Observed location
Frankfurt am Main, DE
Server header
nginx/1.18.0 (Ubuntu)

Serveurs de noms 2

  • andy.ns.cloudflare.com
  • brenna.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-09-21 14:07:20
Valid until
2026-12-20 14:07:19
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-29 10:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprintce160ed97d9fb6360afad44c8bb67568bf418e992506169f9d87ac58d853024c
Certificate names · 1 SANs
  • www.breezeclient.com

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

viewdns.info · 196.251.107.204rapiddns.io

Latest Classified Outcome 2026-10-19 22:27:40 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-19 22:27:40 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 22:35:30 UTC last content: 2026-10-19 22:27:40 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.breezeclient.comDomain record

The original observation time is not recorded for these hostnames.

Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

14 / Les fournisseurs de sécurité 91 ont signalé ce domaine
View on VT
Last analyzed Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
MalwarePatrol
Seclookup
SOCRadar
VIPRE
Webroot

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 breezeclient.com · checked Sep 29, 2026

92
Good
Performance
FCP
2.66s
First Contentful Paint
LCP
2.66s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.66s
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.

breezeclient.com
Résultat enregistré
Cloaked / Filtered
Stored observation history19

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 14
  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→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  11. Availability monitor · Recorded state

    live_content→dns_inactive

    dns_nxdomain

  12. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  13. VirusTotal · Detection count

    13→14

  14. VirusTotal · Detection count

    2→13

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    9 community references

    View source
  3. VirusTotal

    14/91 engine detections

    View source
  4. Abuse report sent

    PD-20260929-BEFFFB

    compliance_abuse@webnic.cc
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    breezeclient.com

    View source

Données factuelles et rapports externes

Analyse de sécurité
URLScan Analyzed VirusTotal 14 det. ChainPatrol URLQuery 2 det. SSL Laboratoires Certificate hostname mismatch CF Radar Malveillant OTX 9 refs WOT ScamAdviser Vérificateur de liste noire URL nulle Sucuri SiteCheck Observatoire MDN
Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260929-BEFFFB Recipient: compliance_abuse@webnic.cc
Page title stored with report: Problem loading page
PDF notice generated
OSINT et renseignement
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certificats WHOIS Wayback Archived
DNS et réseau
nslookup.io DNS bgp.tools ASN /Itinéraire
Référencement naturel et nom de domaine
SpyFu Moz DA/PA Ahrefs Liens entrants
Analyse approfondie
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

6 evidence signal groups linked 1 stored notification records Dernier actif connu
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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Pas un rapport des forces de l'ordre
Recours en matière de nom de domaine
Demandez un examen si vous possédez ce domaine et pensez que la liste est incorrecte
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 breezeclient.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

Vérifier n'importe quel domaine

Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique

Scanner maintenant

Signaler une tentative d'hameçonnage

Signalez les domaines suspects à notre base de données des menaces — protégez la communauté

Signaler

Flux d'alertes en temps réel

Rapports de phishing récents et changements de disponibilité observés

Surveiller

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.

Request a correction or appeal How PhishDestroy works
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/breezeclient.com"
  title="PhishDestroy threat report for breezeclient.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>