VirusTotal
17 / 89 engine detections
レポートを開く“Binance Referral ID: BQ0EAIF5 Great referral program | BQ0EAIF5”
Binanceなりすまし: binancereferralid.github.io — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 17/89 (Criminal IP, alphaMountain.ai, BitDefender, ESET, Emsisoft)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 89 engine detections
レポートを開く悪意あり
レポートを開く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.
PhishDestroy threat report
binancereferralid.github.io is a GitHub Pages site that presents itself as a Binance referral page. It targets people looking to open or fund a Binance account. PhishDestroy first saw it on 2026-09-06 and classifies it as Binance impersonation phishing. As of 2026-10-19 the site was still online and serving content.
The page is titled "Binance Referral ID: BQ0EAIF5 Great referral program | BQ0EAIF5". It repeats a single referral code and uses Binance's name to look like an official or endorsed promotion. The title reads like a referral advertisement, while our classification is impersonation phishing. Pages of this kind borrow an exchange's branding to win trust and then steer visitors toward sign-up or login steps the operator controls. Anyone who enters a Binance email, password or 2FA code on a lookalike flow can lose control of the account and any funds in it.
On 2026-09-16, 17 of 89 VirusTotal engines flagged the site. They include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Emsisoft, alphaMountain.ai and Criminal IP. That is a minority of engines, but several major endpoint and web-filtering vendors agree, which supports the classification beyond a single source. The domain is also listed on the PhishDestroy and Phishunt blocklists.
The site sits on a free github.io subdomain registered through GitHub, Inc. Traffic is served from Fastly's US network, the standard delivery path for GitHub Pages. This setup costs the operator nothing and inherits GitHub's reputation, so the address can look trustworthy to casual visitors. Its Let's Encrypt certificate, issued automatically by GitHub Pages, shows only that the connection is encrypted. It says nothing about who runs the page.
If you entered Binance credentials on this page, change your Binance password right away. Then reset 2FA, review active sessions and API keys, and check your withdrawal address whitelist for entries you did not add. If you registered or deposited through a link from this page, contact Binance support from the official app and do not respond to follow-up messages about bonuses or fees. Security teams should block the domain and report the repository to GitHub for impersonating Binance. Watch for other github.io pages built around the same referral code.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84github.comgithub.iogithubusercontent.comSaved 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 binancereferralid.github.io · checked Sep 6, 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.
binancereferralid.github.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
live_content
content_served
到達可能
No threat flag
View source17/89 engine detections
View sourcebinancereferralid.github.io
View sourcePage captured
View source保存された類似ドメイン:187 件
187 件中 100 件を表示
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 ↗
binancereferralid.github.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.