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 · 생성됨 2014년 3월 30일
HTTP 상태307 Temporary Redirect
기술 세부 정보Provenance & timestamps
최초 발견2026년 9월 14일
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 평판은 이 도메인에 귀속되지 않습니다.
네임서버 1
hugh.ns.cloudflare.com
Location describes the IP network.
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 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 registration알 수 없음
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.
기술 · 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.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
지금 당장 어떻게 해야 할까요?
긴급
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 info-terzor.gitbook.io)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
지역 경찰 — 비록 당장 조치를 취할 수는 없더라도 공식 기록을 남깁니다
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?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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)
