VirusTotal
13 / 89 engine detections
Apri il rapporto“Zimbra Web Client Sign In”
Phishing di credenziali: zimbrapatrikaclient.netlify.app — Contenuto non disponibile (HTTP 404). Riepilogo delle prove: VirusTotal 13/89 (alphaMountain.ai…
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
13 / 89 engine detections
Apri il rapportoMalevolo
Apri il rapportoMalevolo
Apri il rapportono community references
Apri il rapporto80/100
Apri il rapportoNo threat flag
Apri il rapportoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
zimbrapatrikaclient.netlify.app was a credential phishing page that copied the Zimbra Web Client sign-in screen. It targeted employees and members of organizations that run Zimbra for their email. PhishDestroy first detected it on 2026-09-17. The site has been offline since 2026-09-26, and on 2026-10-19 the address still served no content.
The page carried the title "Zimbra Web Client Sign In" and hid inside a free Netlify subdomain built to sound like an official mail client. Victims usually reach pages like this through an email warning of a full mailbox, an expiring password or a pending message, with a link to "sign in". Whatever is typed into the form goes to the operator, not to Zimbra. A stolen webmail login gives the attacker the inbox, the contact list and the password-reset emails for other accounts. Attackers often use that access for internal phishing and invoice fraud.
Within two days of our first detection, 13 of 89 VirusTotal engines flagged the address on 2026-09-19. The flagging vendors include alphaMountain.ai, BitDefender, ESET, Emsisoft, Fortinet, G-Data, Gridinsoft and Kaspersky. Several established vendors reaching the same conclusion independently is strong backing for a short-lived phishing page. urlscan.io gave a malicious verdict and identified the Zimbra brand on the page. The domain is listed on the PhishDestroy blocklist.
The operator registered nothing. The page ran on a Netlify subdomain, so it inherited the platform's reputation and HTTPS at no cost. Traffic was served from Amazon.com, Inc. infrastructure in Germany. This throwaway setup is cheap to replace, and the site lasted roughly nine days after we spotted it before going dark. Expect the same lure to reappear under new free-hosting names.
If you entered your Zimbra credentials on this page, change your mail password immediately. Change it on every other service where you reused it. Enable two-factor authentication if your provider supports it. Check your mailbox for forwarding rules, filters and sent messages you did not create, and tell your IT team so they can end active sessions. Watch for follow-up phishing sent to your contacts from your account. Defenders should block the hostname, search mail logs for messages linking to it, and reset credentials for any user who clicked through.
La reputazione Edge-IP non è attribuita a questo dominio.
Location describes the IP network.
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478netlify.appSaved 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 zimbrapatrikaclient.netlify.app · checked Sep 17, 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.
zimbrapatrikaclient.netlify.app
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Raggiungibile→Non disponibile
12→13
No threat flag
View source13/89 engine detections
View sourcezimbrapatrikaclient.netlify.app
View sourceListed 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 ↗
zimbrapatrikaclient.netlify.app)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.