VirusTotal
6 / 91 engine detections
Ouvrir le rapport“Surge — AI Workforce Platform”
Hameçonnage: surgehq.io — Dernier actif connu (HTTP 307). Résumé des preuves: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
6 / 91 engine detections
Ouvrir le rapport4 community references
Ouvrir le rapportprovider verdict: clean
Ouvrir le rapport80/100
Ouvrir le rapportNo threat flag
Ouvrir le rapportNo malicious flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
surgehq.io presents itself as "Surge — AI Workforce Platform", borrowing the name and look of an AI workforce service to win the trust of businesses and individual users. PhishDestroy classifies it as an impersonation phishing page and first flagged it on 2026-09-28. As of 2026-10-19 the domain was still live and redirecting visitors elsewhere, so the lure remains active.
Impersonation pages like this copy a real or plausible product's branding, here an AI workforce platform, so that visitors feel they are on an official site. The usual goal is to get people to sign in, register, connect accounts or pay for a plan, handing account credentials, personal details or payment information to the operators. Because the domain now redirects, visitors may be sent on to a different page that carries out the actual collection. Victims risk losing account access, money paid for a service that does not exist, and any data they typed in.
On 2026-10-03, 6 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar, URLQuery and VIPRE. That is a modest count, but it comes from several unrelated vendors that reached the same conclusion independently. The domain also appears in 4 AlienVault OTX threat pulses, where other researchers have tied it to malicious activity, and it is listed on the PhishDestroy blocklist.
The domain was registered through Namecheap on 2026-06-05, roughly 115 days before PhishDestroy detected it. That gap suggests it was set up in advance and given time to age before the campaign drew attention. It resolves to 216.198.79.1 on Amazon's network in the United States. Its Let's Encrypt certificate is free and issued automatically, so the browser padlock shows only that the connection is encrypted and says nothing about whether the site is legitimate.
If you signed in or registered on surgehq.io, change that password immediately, along with the password on any other account where you reused it, and turn on two-factor authentication. If you entered card or bank details, contact your bank to block the card and dispute any charges, and watch your statements closely. Treat follow-up emails or messages that mention Surge with suspicion, and reach the real service only through channels you have verified yourself. Defenders should block the domain and its IP at the DNS, proxy and email gateway level, and search logs for any users who visited or were redirected through it.
La réputation Edge-IP n’est pas attribuée à ce domaine.
dns1.registrar-servers.comdns2.registrar-servers.cominbound-smtp.us-east-1.amazonaws.compriority 9Location describes the IP network.
2a9e88b4ea0acaa55844f0217273dcf56a75812692ce282e26025527f7f9422aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
app.surgehq.ioDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of surgehq.io · checked Sep 28, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
redirected→protected
http_access_restricted · access_restriction
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
redirected→protected
http_access_restricted · access_restriction
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
4→5
3→4
2→3
Accessible
No threat flag
View source6/91 engine detections
View source4 community references
View sourcePage captured
View sourcesurgehq.io
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
surgehq.io
Listed domains receive at least one abuse report; this entry has no retained notification history.
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.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
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 ↗
surgehq.io)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.
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
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
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.