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.
Registration (base domain)gitbook.io · Created Mar 30, 2014
HTTP Status307 Temporary Redirect
Technical detailsProvenance & timestamps
First DetectedSep 14, 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
Edge-IP reputation is not attributed to this domain.
Nameservers 1
hugh.ns.cloudflare.com
Location describes the IP network.
TLS certificate
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 fingerprintf3e0d20bcdcb0f6afa89f62c0f4ef0ea0ddd7a7445d5cc7ae8b2e212568ea348Certificate 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 HTTP observationRedirectingHTTP redirect observed80%2026-10-19 10:08:04 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-19 10:08:04 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.
Technologies · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · info-terzor.gitbook.io
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
1 evidence signal groups linked0 stored notification recordsLast known active
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including info-terzor.gitbook.io)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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.
(US)
