VirusTotal
13 / 89 engine detections
रिपोर्ट खोलेंGoogle की नकल: info-terzor.gitbook.io — अंतिम ज्ञात सक्रिय (HTTP 307). साक्ष्य सारांश: VirusTotal 13/89 (alphaMountain.ai, BitDefender, CyRadar, Ermes, ESET)…
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
13 / 89 engine detections
रिपोर्ट खोलेंदुर्भावनापूर्ण
रिपोर्ट खोलेंDBL_ABUSED_PHISH
no community references
रिपोर्ट खोलेंNo threat flag
रिपोर्ट खोलेंResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
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.
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.
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.
एज-आईपी प्रतिष्ठा इस डोमेन के लिए जिम्मेदार नहीं है।
hugh.ns.cloudflare.comLocation describes the IP network.
f3e0d20bcdcb0f6afa89f62c0f4ef0ea0ddd7a7445d5cc7ae8b2e212568ea348gitbook.ioSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
पहुँच योग्य
No threat flag
View source13/89 engine detections
View sourceinfo-terzor.gitbook.io
View source1 सामुदायिक रिपोर्ट
श्रेणीIMPERSONATION
Brand abuse: impersonation, fake affiliation, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
info-terzor.gitbook.io
Listed domains receive at least one abuse report; this entry has no retained notification history.
यदि आपने खाता क्रेडेंशियल, व्यक्तिगत या भुगतान जानकारी दर्ज की है, या इस डोमेन से कोई फ़ाइल डाउनलोड की है, तो तुरंत कार्रवाई करें। घटना की रिपोर्ट करने और अपनी सुरक्षा करने में आपकी सहायता के लिए नीचे संसाधन दिए गए हैं।
आधिकारिक साइबर अपराध संपर्क, या एक शिकायत ड्राफ्ट बनाएं → प्राप्त करने के लिए अपना देश चुनें।
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
info-terzor.gitbook.io)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
संग्रहीत ब्लॉकलिस्ट, WHOIS, DNS और सार्वजनिक स्कैन साक्ष्य का उपयोग करके खतरे का विश्लेषण
अभी स्कैन करेंसंदिग्ध डोमेन हमारे थ्रेट डेटाबेस में जमा करें — समुदाय की सुरक्षा करें
रिपोर्ट करेंहाल की फ़िशिंग रिपोर्टें और उपलब्धता में परिवर्तन देखे गए
निगरानी करेंलाइव खतरों की निगरानी करें या यदि आपको लगता है कि यह एक गलत सकारात्मक है तो इस लिस्टिंग को चुनौती दें।
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.