Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
surgehq.io favicon

surgehq.io

“Surge — AI Workforce Platform”

Registrar
Namecheap
Resolved IP
216.198.79.1
Registered
05/06/2026
PhishDestroy assessment Kritis
Ketersediaan Terakhir diketahui aktif Pengamatan keterjangkauan tersimpan terbaru Teramati · HTTP probe
Deteksi Total Virus: 6/91 Jenis penipuan: Impersonation
OTX: 4 refs 28/09/2026 CDN
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 6. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Ringkasan laporan

Phishing: surgehq.io — Terakhir diketahui aktif (HTTP 307). Ringkasan bukti: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar…

Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.

Source evidenceVirusTotal 6 / 91 · OTX 4 references 6 sources

VirusTotal

6 / 91 engine detections

Buka laporan

Google Safe Browsing

No threat flag

Buka laporan

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

Analysis

Kritis
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

Tangkapan tersimpan · 3 captures

Domain details

Domain
URLScan verdict Analisis selesai score 0 report ↗
IP Context Vercel shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomaindrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Namecheap US(US)
Kontak penyalahgunaanabuse@vercel.com
PendaftaranDibuat 05/06/2026 (137d) — Expires 05/06/2027
Status HTTP307 Temporary Redirect
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi28/09/2026
DOM Analysisanalyzed 09/10/2026score 88/100
Submitted URLhttp://surgehq.io/
Favicon Hash
Observed page title
Surge — AI Workforce Platform
Sertifikat TLS
Diterbitkan oleh 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

Reputasi Edge-IP tidak dikaitkan dengan domain ini.

Server nama 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.

Sertifikat 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 Tidak diketahui
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.

Teknologi · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

6 / Vendor keamanan 91 menandai domain ini
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar
URLQuery
VIPRE
Analisis Performa Situs

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

    Tidak diketahui→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

Earlier observations 19
  1. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  6. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  7. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  13. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  14. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  15. Availability monitor · Recorded state

    Tidak diketahui→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

    Dapat dijangkau

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

Bukti & Laporan Eksternal

Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

5 evidence signal groups linked 0 stored notification records Terakhir diketahui aktif

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.

Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.

Official reporting routes

Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial. Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →

Laporkan kepada Pihak Berwenang di Daerah Anda

Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.

Direktori 97 negara

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

Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
After a phishing incident

Rekomendasi & Saran bagi Para Korban

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

Apa yang harus saya lakukan segera?

Mendesak

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

  • Ubah semua kata sandi — email, akun Exchange, apa pun yang menggunakan kata sandi yang sama
  • Aktifkan 2FA menggunakan aplikasi otentikator (bukan SMS). Nonaktifkan pemulihan berbasis SMS
  • Kartu pembeku jika Anda telah memasukkan detail perbankan di situs phishing tersebut

Informasi apa saja yang sebaiknya saya kumpulkan untuk laporan saya?

Pedoman 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.
  • Tanggal dan waktu yang tepat — dari setiap transaksi dan kontak pertama dengan penipu
  • Tangkapan layar — situs web penipuan, pesan obrolan, email, transaksi dompet digital, media sosial
  • Semua URL & domain digunakan oleh penipu (termasuk surgehq.io)
  • Komunikasi — email, pesan teks, nomor telepon, dan nama pengguna yang digunakan oleh penipu tersebut

Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.

Ke mana saya harus melaporkan penipuan ini?

  • FBI IC3 — Pusat Pengaduan Kejahatan Internet (Laporan tingkat federal AS)
  • Europol — Pelaporan kejahatan siber di Eropa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polisi setempat — membuat catatan resmi, meskipun mereka tidak dapat bertindak segera

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?

  • Situs web palsu — salinan yang persis sama dengan situs asli, dengan domain yang sedikit diubah
  • Pemotongan babi — kepercayaan yang dibangun selama beberapa minggu melalui Telegram/WhatsApp/aplikasi kencan, lalu uangnya dicuri
  • Penipuan pemulihan — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Penipuan yang didukung oleh kecerdasan buatan — deepfakes, serangan phishing otomatis, dan situs yang dihasilkan oleh kecerdasan buatan (AI) yang membuat penipuan semakin sulit dideteksi

Bagaimana cara saya melindungi diri di masa depan?

  • Tandai situs resmi — jangan pernah mengklik tautan dari email, pesan langsung (DM), atau iklan
  • Memverifikasi domain — periksa PhishDestroy Sebelum berinteraksi. Periksa HTTPS, ejaan, dan usia domain
  • "Terlalu bagus untuk jadi kenyataan" = penipuan — imbal hasil yang dijamin, dukungan dari selebriti, tenggat waktu yang mendesak

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

Tetap Terinformasi, Tetap Aman

Pantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive

Pemberitahuan Ancaman Real-Time Ajukan Banding Terhadap Iklan Ini
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

Sematkan Laporan Ini

Bagikan informasi ancaman ini di situs web atau blog Anda

embed.html
<iframe
  src="https://phishdestroy.io/id/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>