Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
info-terzor.gitbook.io favicon

info-terzor.gitbook.io

Registrar
Cloudflare
Resolved IP
104.18.40.47
Registered
30/03/2014
PhishDestroy assessment Kritis
Ketersediaan Terakhir diketahui aktif Pengamatan keterjangkauan tersimpan terbaru Teramati · HTTP probe
Deteksi Total Virus: 13/89 Spamhaus DBL: DBL_ABUSED_PHISH Label merek otomatis: Google
14/09/2026 CDN
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 13. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
engine detections
Google Safe Browsing
Domain age
Ringkasan laporan

Peniruan Google: info-terzor.gitbook.io — Terakhir diketahui aktif (HTTP 307). Ringkasan bukti: VirusTotal 13/89 (alphaMountain.ai, BitDefender, CyRadar…

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

Source evidenceVirusTotal 13 / 89 5 sources

VirusTotal

13 / 89 engine detections

Buka laporan

Spamhaus DBL

DBL_ABUSED_PHISH

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.

Intelijen Keamanan Jaringan
CF Cloudflare Radar Verdict Berbahaya
Phishing

Analysis

Kritis
VirusTotal
13 / 89

PhishDestroy threat report

Overview

info-terzor.gitbook.io is an impersonation phishing page published as a subdomain of GitBook, the documentation platform that many legitimate crypto projects use for their official docs. The "info-" prefix is meant to look like a help or information portal, aimed at users searching for guidance on a project. PhishDestroy first flagged it on 2026-09-14. As of 2026-10-19 the site was still alive and redirecting visitors onward.

How the scam works

Impersonation pages on documentation hosts borrow the platform's trusted look. A visitor who lands there through a search result, a social media reply or a fake support message sees what appears to be official instructions. Those instructions then push the visitor toward a sign-in form, a seed-phrase "verification" step or a wallet connection. Because this page redirects, the GitBook address works as a clean-looking front door, and the actual theft happens at the destination. Victims typically lose account credentials, recovery phrases or wallet funds.

Evidence

On 2026-09-23, 13 of 89 VirusTotal engines flagged the page. They included BitDefender, ESET, G-Data, Emsisoft, alphaMountain.ai, CyRadar, Ermes and LevelBlue, so the detection comes from several independent security vendors. Spamhaus lists the domain in its DBL as an abused-legitimate phishing host, meaning the parent platform is sound but this subdomain is being misused. The page also appears on the PhishDestroy blocklist.

Infrastructure

The 2014-03-30 registration date belongs to GitBook's parent domain, not to the operator, so the domain's age says nothing about how long this scam has been running. Cloudflare, Inc. is both registrar and hosting network, with the serving address located in Canada. The Google Trust Services certificate comes from the platform itself, so the padlock in the browser does not show that the page is genuine.

What to do

If you typed a password or login code after visiting, change that password immediately, sign out of all sessions, and turn on app-based 2FA. If you entered a seed phrase anywhere this page sent you, treat that wallet as compromised and move the funds to a new wallet with a new phrase. If it led you to connect a wallet, revoke any approvals you granted. Defenders should block the subdomain and its redirect targets, report it to GitBook for removal, and remind users that real projects never ask for a recovery phrase through a docs page.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
Registrar (base domain) Cloudflare US(US)
Registration (base domain)gitbook.io · Dibuat 30/03/2014
Status HTTP307 Temporary Redirect
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi14/09/2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.18.40.47
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Reputasi Edge-IP tidak dikaitkan dengan domain ini.

Server nama 1

  • hugh.ns.cloudflare.com

Location describes the IP network.

Sertifikat TLS

Issuer
Google Trust Services / WE1
Valid from
2026-09-14 22:03:00
Valid until
2026-12-13 23:02:54
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-21 04:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintf3e0d20bcdcb0f6afa89f62c0f4ef0ea0ddd7a7445d5cc7ae8b2e212568ea348
Certificate names · 1 SANs
  • gitbook.io

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-20 10:07:14 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-20 10:07:14 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-10-20 10:07:14 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.
Teknologi · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

13 / Vendor keamanan 89 menandai domain ini
View on VT
Last analyzed First positive detection Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CyRadar
Ermes
ESET
Emsisoft
G-Data
LevelBlue
Lionic
Netcraft
PhishFort
Sophos
Webroot
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 history17

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 12
  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

  6. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  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 · First collection record

    Dapat dijangkau

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    13/89 engine detections

    View source
  3. Added to PhishDestroy

    info-terzor.gitbook.io

    View source

Intelijen komunitas

1 laporan komunitas

KategoriIMPERSONATION

Brand abuse: impersonation, fake affiliation, impersonating Trezor

Check for cloaking

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

info-terzor.gitbook.io

Bukti & Laporan Eksternal

Third-Party Detection — ChainAbuse
1 report filed for info-terzor.gitbook.io · category: Impersonation · source checked
Flagged by automated brand-abuse detection on Sep 14, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

1 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 info-terzor.gitbook.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/info-terzor.gitbook.io"
  title="PhishDestroy threat report for info-terzor.gitbook.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>