Ir para o relatório de segurança
Segurança de domínio e inteligência contra ameaças
surgehq.io favicon

surgehq.io

“Surge — AI Workforce Platform”

Registrador
Namecheap
Resolved IP
216.198.79.1
Registered
05/06/2026
PhishDestroy assessment Crítico
Disponibilidade Último ativo conhecido Última observação de acessibilidade armazenada Observado · HTTP probe
Detecções do VirusTotal: 6/91 Tipo de golpe: Impersonation
OTX: 4 refs 28/09/2026 CDN
API
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 6. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Resumo do relatório

Phishing: surgehq.io — Último ativo conhecido (HTTP 307). Resumo das evidências: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar…

A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.

Source evidenceVirusTotal 6 / 91 · OTX 4 references 6 sources

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

Analysis

Crítico
VirusTotal
6 / 91
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura armazenada · 3 captures

Domain details

Domínio
URLScan verdict Análise concluída score 0 report ↗
IP Context Vercel shared edge origin IP hidden A reputação do Edge-IP não é atribuída a este domínio.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomíniosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Namecheap US(US)
Contato para abusosabuse@vercel.com
Registro da ICANNICANN Lookup (RDAP) →
RegistroCriado 05/06/2026 (137d) — Expires 05/06/2027
Status HTTP307 Temporary Redirect
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez28/09/2026
DOM Analysisanalyzed 09/10/2026score 88/100
Submitted URLhttp://surgehq.io/
Favicon Hash
Observed page title
Surge — AI Workforce Platform
Certificado TLS
Emitido por Let's Encrypt / YR1 · stored validity ends in 77 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.198.79.1
Network ASN
AS16509
Organization
Lefkoff Industries
Observed location
Atlanta, US
Server header
Vercel

A reputação do Edge-IP não é atribuída a este domínio.

Servidores de nomes 2

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

Mail routing 1 MX record

  • inbound-smtp.us-east-1.amazonaws.compriority 9

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YR1
Valid from
2026-10-08 15:49:45
Valid until
2027-01-06 15:49:44
Validity
Within stored validity dates
Collection time
2026-10-11 07:02:09 UTC
Collection source
PhishDestroy collector
Certificate fingerprint2a9e88b4ea0acaa55844f0217273dcf56a75812692ce282e26025527f7f9422a

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-19 22:32:47 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-19 22:32:47 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-10-19 22:35: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.
Recorded subdomains1

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

  • app.surgehq.ioDomain record

The original observation time is not recorded for these hostnames.

Tecnologias · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Análise do VirusTotal

6 / Os fornecedores de segurança 91 sinalizaram este domínio
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar
URLQuery
VIPRE
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of surgehq.io · checked Sep 28, 2026

88
Needs Work
Performance
FCP
1.06s
First Contentful Paint
LCP
3.82s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
7ms
Total Blocking Time
SI
2.71s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Stored observation history24

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

    Desconhecido→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

Earlier observations 19
  1. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  6. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  7. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  13. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  14. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  15. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  16. VirusTotal · Detection count

    4→5

  17. VirusTotal · Detection count

    3→4

  18. VirusTotal · Detection count

    2→3

  19. Availability monitor · First collection record

    Acessível

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/91 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    surgehq.io

    View source

Check for cloaking

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

surgehq.io

Evidências e relatórios externos

Análise aprofundada
Help & reporting

Você foi afetado por este site?

5 evidence signal groups linked 0 stored notification records Último ativo conhecido

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.

Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.

Official reporting routes

Cuidado com os golpistas que prometem recuperação! Os criminosos podem entrar em contato novamente com as vítimas fingindo ser investigadores, advogados ou agentes de recuperação. Não pague taxas antecipadas nem compartilhe credenciais. Saiba mais sobre fraudes relacionadas à recuperação →

Notifique as autoridades locais

Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.

Diretório de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Rascunho assistido por IA – os detalhes do incidente são processados pelo provedor de IA · Revise e envie você mesmo
After a phishing incident

Recomendações e orientações para as vítimas

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

O que devo fazer agora mesmo?

Urgente

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

  • Alterar todas as senhas — e-mail, contas do Exchange, qualquer coisa que use a mesma senha
  • Ativar a autenticação de dois fatores usando um aplicativo autenticador (não por SMS). Desative a recuperação por SMS
  • Cartões de congelamento se você inseriu dados bancários no site de phishing

Que informações devo coletar para o meu relatório?

Diretrizes do 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.
  • Datas e horários exatos — de cada transação e do primeiro contato com o golpista
  • Capturas de tela — sites fraudulentos, mensagens de bate-papo, e-mails, transações em carteiras digitais, redes sociais
  • Todas as URLs e domínios utilizado pelo golpista (incluindo surgehq.io)
  • Comunicações — e-mails, mensagens de texto, números de telefone e nomes de usuário que o golpista utilizou

Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.

A quem devo denunciar o golpe?

  • FBI IC3 — Centro de Denúncias de Crimes na Internet (sistema federal de denúncias dos EUA)
  • Europol — Relatórios sobre crimes cibernéticos na Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polícia local — cria um registro oficial, mesmo que não possam agir imediatamente

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?

  • Sites falsos — clones idênticos, até o último pixel, de sites legítimos, com domínios ligeiramente alterados
  • Abate de suínos — confiança construída ao longo de semanas pelo Telegram, WhatsApp e aplicativos de namoro; em seguida, o dinheiro foi roubado
  • Golpes relacionados à recuperação — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Golpes baseados em IA — deepfakes, phishing automatizado e sites gerados por IA, o que torna a fraude mais difícil de detectar

Como posso me proteger no futuro?

  • Adicione os sites oficiais aos favoritos — nunca clique em links de e-mails, mensagens diretas ou anúncios
  • Verificar domínios — verificar PhishDestroy antes de interagir. Verifique se o site usa HTTPS, a ortografia e a idade do domínio
  • "Bom demais para ser verdade" = golpe — retornos garantidos, endossos de celebridades, prazos urgentes

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

Mantenha-se informado, mantenha-se seguro

Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo

Feed de ameaças em tempo real Recorrer deste anúncio
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

Incorporar este relatório

Compartilhe essas informações sobre ameaças em seu site ou blog

embed.html
<iframe
  src="https://phishdestroy.io/pt-br/embed/domain/surgehq.io"
  title="PhishDestroy threat report for surgehq.io"
  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>