VirusTotal
15 / 89 engine detections
보고서 열기“BitBuy Login | us”
bitbuogin.gitbook.io — 마지막으로 알려진 활성 (HTTP 307). 사기 유형: Impersonation. 증거 요약: VirusTotal 15/89 (ChainPatrol, alphaMountain.ai, BitDefender, CyRadar, ESET); 2 external blocklist matches (MetaMask, SEAL); CF Radar malicious; PhishDestroy score 100/100. 등록기관: GitBook.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
15 / 89 engine detections
보고서 열기악성
보고서 열기15/100
보고서 열기no community references
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
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.
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.
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.
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.
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.
urlscan.io scan and screenshot: https://urlscan.io/result/019f6a57-1e66-72f4-a8e7-3ecec184807d/
VirusTotal report: https://www.virustotal.com/gui/domain/bitbuogin.gitbook.io
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=bitbuogin.gitbook.io
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
Last checked
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
hugh.ns.cloudflare.comLocation describes the IP network.
d76aa1094c3d1ca19014ac824313b04e833289dec61fbca06aa6f92bad9464adgitbook.ioSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of bitbuogin.gitbook.io · checked Sep 11, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
bitbuogin.gitbook.io
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
No threat flag
View source15/89 engine detections
View sourcebitbuogin.gitbook.io
View sourceListed 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 ↗
bitbuogin.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
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.