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

bitbuogin.gitbook.io

“BitBuy Login | us”

Registrar
GitBook
Resolved IP
172.64.147.209
Registered
30/03/2014
PhishDestroy assessment Critico
Disponibilità Ultimo attivo conosciuto Ultima osservazione di raggiungibilità memorizzata Osservato · HTTP probe
Rilevamenti VirusTotal: 15/89 Corrispondenze della blocklist memorizzate: 2 Tipo di truffa: Impersonation
11/09/2026 CDN
API
Questo dominio è stato segnalato come dannoso
Motori di sicurezza che segnalano un rilevamento: 15. Blocklist pubbliche che segnalano una corrispondenza: 2. Prestare estrema cautela: non inserire credenziali o informazioni personali.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Riepilogo del rapporto

Phishing: bitbuogin.gitbook.io — Ultimo attivo conosciuto (HTTP 307). Riepilogo delle prove: VirusTotal 15/89 (ChainPatrol, alphaMountain.ai, BitDefender…

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

Source evidenceVirusTotal 15 / 89 6 sources

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
15 / 89
Page captures
2

PhishDestroy threat report

Overview

bitbuogin.gitbook.io is an impersonation phishing page posing as the sign-in portal of Bitbuy, the cryptocurrency exchange. Its page title, "BitBuy Login | us", is meant to catch exchange customers who search for their login page or follow a link from a message. PhishDestroy first detected it on 2026-09-11. As of 2026-10-19 the site was still online and its content was reachable through a redirect.

How the scam works

Fake exchange login pages copy the look of the real sign-in screen and collect whatever the visitor types, usually an email address, a password and often a one-time 2FA code. The attacker then replays those details on the genuine exchange, takes over the account and moves out any crypto or cash before the owner notices. Publishing the lure as a documentation page on a well-known platform lends it a familiar address that can slip past a quick glance. The victim loses access to the account and every balance it holds.

Evidence

On 2026-09-20, 15 of 89 VirusTotal engines flagged the address as malicious. The flagging vendors include ChainPatrol, alphaMountain.ai, BitDefender, CyRadar, ESET, Emsisoft, Forcepoint ThreatSeeker and G-Data, which means crypto-focused and general security vendors reached the same verdict on their own. The page also appears on the MetaMask and SEAL blocklists alongside PhishDestroy, so wallet users and crypto security teams get warnings from several directions.

Infrastructure

The 2014-03-30 registration date belongs to GitBook's own platform domain, and GitBook is listed as registrar, so the age of the address says nothing about when the operator set up this page. The phishing content sits on a user-created subdomain. Traffic is served through Cloudflare, Inc. from an address located in Canada, which matches the home market of the brand being imitated.

What to do

If you entered your Bitbuy email and password on this page, sign in to Bitbuy only by typing the address yourself, change your password at once and reset your two-factor authentication. Check the account for unfamiliar logins, withdrawals or new withdrawal addresses, then contact Bitbuy support so they can lock the account if needed. Change the password anywhere else you reused it, and secure the email account linked to Bitbuy. Defenders should block the subdomain, report it to GitBook for removal and watch for other lookalike documentation pages that use Bitbuy branding.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Presente View source
PhishDestroy PhishDestroy list View source
SEAL Presente View source

Last checked

Acquisizione salvata · 2 captures

Domain details

Dominio
URLScan verdict Analisi completata score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La reputazione Edge-IP non è attribuita a questo dominio.
Registrar (base domain) GitBook
Registration (base domain)gitbook.io · Creato 30/03/2014
Stato HTTP307 Temporary Redirect
Dettagli tecniciProvenance & timestamps
Rilevato per la prima volta11/09/2026
DOM Analysisanalyzed 11/09/2026score 100/1001 brand signal
Submitted URLhttp://bitbuogin.gitbook.io/
Favicon Hash
Observed page title
BitBuy Login | us
Automated brand references
Across
Certificato TLS
Emesso da Google Trust Services / WE1

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.64.147.209
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-07-17 18:03:25
Valid until
2026-10-15 19:03:12
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-09-11 10:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd76aa1094c3d1ca19014ac824313b04e833289dec61fbca06aa6f92bad9464ad
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:35 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:35 UTC
RDAP registration Sconosciuto
Observed timeline last reachable: 2026-10-20 10:07:35 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 · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Segnala questo dominio Invia le prove e contribuisci a proteggere gli altri

Analisi di VirusTotal

15 / I fornitori di sicurezza 89 hanno contrassegnato questo dominio
View on VT
Last analyzed Previous stored snapshot: 9 detections
ChainPatrol
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
G-Data
Kaspersky
LevelBlue
Lionic
Netcraft
Sophos
VIPRE
Webroot
Analisi delle prestazioni del sito

Google PageSpeed Insights — mobile performance audit of bitbuogin.gitbook.io · checked Sep 11, 2026

79
Needs Work
Performance
FCP
2.43s
First Contentful Paint
LCP
4.83s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
93ms
Total Blocking Time
SI
2.51s
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.

Check for cloaking

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

bitbuogin.gitbook.io
Risultato salvato
Keitaro TDS
Stored observation history16

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

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    15/89 engine detections

    View source
  3. Added to PhishDestroy

    bitbuogin.gitbook.io

    View source

Dati e relazioni esterne

Analisi approfondita
Help & reporting

Questo sito ti ha influenzato in qualche modo?

4 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 bitbuogin.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/bitbuogin.gitbook.io"
  title="PhishDestroy threat report for bitbuogin.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>