Vai al rapporto di sicurezza
Sicurezza del dominio e intelligence sulle minacce
info-terzor.gitbook.io favicon

info-terzor.gitbook.io

Registrar
Cloudflare
Resolved IP
104.18.40.47
Registered
30/03/2014
PhishDestroy assessment Critico
Disponibilità Ultimo attivo conosciuto Ultima osservazione di raggiungibilità memorizzata Osservato · HTTP probe
Rilevamenti VirusTotal: 13/89 Spamhaus DBL: DBL_ABUSED_PHISH Etichetta automatica del marchio: Google
14/09/2026 CDN
API
Questo dominio è stato segnalato come dannoso
Motori di sicurezza che segnalano un rilevamento: 13. Prestare estrema cautela: non inserire credenziali o informazioni personali.
VirusTotal
engine detections
Google Safe Browsing
Domain age
Riepilogo del rapporto

Imitazione di Google: info-terzor.gitbook.io — Ultimo attivo conosciuto (HTTP 307). Riepilogo delle prove: VirusTotal 13/89 (alphaMountain.ai, BitDefender…

L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.

Source evidenceVirusTotal 13 / 89 5 sources

Spamhaus DBL

DBL_ABUSED_PHISH

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

Informazioni sulla sicurezza di rete
CF Cloudflare Radar Verdict Malevolo
Phishing

Analysis

Critico
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

Dominio
IP Context Cloudflare shared edge origin IP hidden La reputazione Edge-IP non è attribuita a questo dominio.
Registrar (base domain) Cloudflare US(US)
Registration (base domain)gitbook.io · Creato 30/03/2014
Stato HTTP307 Temporary Redirect
Dettagli tecniciProvenance & timestamps
Rilevato per la prima volta14/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

La reputazione Edge-IP non è attribuita a questo dominio.

Nameserver 1

  • hugh.ns.cloudflare.com

Location describes the IP network.

Certificato 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 Sconosciuto
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.
Tecnologie · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Segnala questo dominio Invia le prove e contribuisci a proteggere gli altri

Analisi di VirusTotal

13 / I fornitori di sicurezza 89 hanno contrassegnato questo dominio
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

    Sconosciuto→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

Earlier observations 12
  1. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Sconosciuto→redirected

    http_redirect

  12. Availability monitor · First collection record

    Raggiungibile

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

Intelligence della comunità

1 segnalazione della comunità

CategoriaIMPERSONATION

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

Dati e relazioni esterne

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).
Analisi approfondita
Help & reporting

Questo sito ti ha influenzato in qualche modo?

1 evidence signal groups linked 0 stored notification records Ultimo attivo conosciuto

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

Official reporting routes

Europol
Trova il canale di segnalazione ufficiale per il tuo paese dell'UE
National police directory
Find your country
Attenzione ai truffatori che promettono il recupero dei fondi! I criminali possono contattare nuovamente le vittime fingendo di essere investigatori, avvocati o agenti di recupero. Non pagare commissioni anticipate né condividere credenziali. Scopri di più sulle frodi relative ai sussidi di recupero →

Segnalalo alle autorità locali

Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.

Elenco di 97 paesi

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

Bozza assistita dall'intelligenza artificiale: i dettagli dell'incidente vengono elaborati dal fornitore di intelligenza artificiale · Controllalo e invialo tu stesso
After a phishing incident

Raccomandazioni e consigli per le vittime

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

Cosa devo fare subito?

Urgente

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

  • Modifica tutte le password — e-mail, account Exchange, qualsiasi servizio che utilizzi la stessa password
  • Abilita l'autenticazione a due fattori (2FA) utilizzando un'app di autenticazione (non via SMS). Disattiva il recupero tramite SMS
  • Carte congelate se hai inserito i tuoi dati bancari sul sito di phishing

Quali informazioni devo raccogliere per la mia relazione?

Linee guida dell'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.
  • Date e orari esatti — di ogni transazione e del primo contatto con il truffatore
  • Schermate — siti web truffaldini, messaggi in chat, e-mail, transazioni tramite portafoglio digitale, social media
  • Tutti gli URL e i domini utilizzato dal truffatore (tra cui info-terzor.gitbook.io)
  • Comunicazioni — e-mail, SMS, numeri di telefono, nomi utente utilizzati dal truffatore

Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.

A chi devo segnalare la truffa?

  • FBI IC3 — Internet Crime Complaint Center (sistema di segnalazione federale degli Stati Uniti)
  • Europol — Segnalazioni relative alla criminalità informatica in Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polizia locale — crea un documento ufficiale, anche se non è in grado di agire immediatamente

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?

  • Siti web fasulli — cloni perfetti, al pixel, di siti legittimi con domini leggermente modificati
  • Macellazione dei suini — fiducia conquistata nel corso di settimane tramite Telegram/WhatsApp/app di incontri, per poi rubare i soldi
  • Truffe legate al recupero dei fondi — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Truffe basate sull'intelligenza artificiale — i deepfake, il phishing automatizzato e i siti generati dall’intelligenza artificiale rendono più difficile individuare le frodi

Come posso proteggermi in futuro?

  • Aggiungi i siti ufficiali ai preferiti — Non cliccare mai sui link contenuti nelle e-mail, nei messaggi diretti o negli annunci pubblicitari
  • Verifica i domini — controllare PhishDestroy prima di interagire. Verifica l'HTTPS, l'ortografia e l'età del dominio
  • "Troppo bello per essere vero" = truffa — rendimenti garantiti, testimonial di personaggi famosi, scadenze urgenti

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

Rimani informato, rimani al sicuro

Controlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo

Feed in tempo reale sulle minacce Contesta questo annuncio
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

Incorpora questo rapporto

Condividi queste informazioni sulle minacce sul tuo sito web o sul tuo blog

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