VirusTotal
5 / 92 engine detections
レポートを開く“DityBit - Mobile Crypto Exchange Preview”
フィッシング: ditybit.us — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 5/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar); Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 92 engine detections
レポートを開くDBL_PHISH
4 community references
レポートを開くprovider verdict: clean
レポートを開く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
ditybit.us presents itself as "DityBit - Mobile Crypto Exchange Preview", a supposed mobile trading app aimed at people looking for a new place to buy and trade crypto. PhishDestroy classifies it as an impersonation phishing page and first flagged it on 2026-08-28. As of 2026-10-19 the site was still online and serving its content, so anyone who finds it through ads, social posts or direct messages can still reach it.
Sites like this borrow the look of a crypto exchange and pitch an early or "preview" version of a mobile app to make sign-up feel exclusive and urgent. Victims are pushed to register, hand over email and password, and then fund an account or connect a wallet to start trading. Any balance shown afterwards exists only on the scammer's screen. Attempts to withdraw are typically met with demands for extra "fees" or "verification deposits" that are simply taken too. Victims can lose deposited crypto, login credentials, and wallet funds if they approve transactions the site requests.
Several crypto-focused defenders agree on this one: MetaMask and SEAL both list the domain alongside PhishDestroy, and Spamhaus carries it in its domain blocklist as phishing. On VirusTotal, 5 of 92 engines flagged it as of 2026-10-12, namely alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That count is low, so many generic security tools may still let the page load without warning. Four AlienVault OTX threat pulses also reference the domain.
The domain was registered through Hosting Concepts B.V. d/b/a Registrar.eu on 2026-08-27, just one day before PhishDestroy caught it, which fits a site built for immediate use. It sits behind Cloudflare, which places it on a Canadian address. Because Cloudflare acts as a proxy, that address belongs to the network edge, and the real origin server stays hidden from visitors.
Do not send any further money to ditybit.us. If the site asks for a "withdrawal fee" or tax to release your balance, treat it as a second theft attempt. If you registered, change that password everywhere you reused it and turn on two-factor authentication. If you connected a wallet, revoke any approvals the site obtained and move remaining assets to a fresh wallet. Report the deposit transactions to your exchange or local police. Defenders should block the domain at DNS and proxy level and watch for lookalike DityBit domains.
Last checked
Edge-IP の評判はこのドメインに起因しません。
igor.ns.cloudflare.comjill.ns.cloudflare.comsmtp.google.compriority 1Location describes the IP network.
56195742a356074a34343403c9e589365aa3d0076ec62ca5cb1b620bb844b224Saved 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 ditybit.us · checked Aug 28, 2026
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.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
2→4
1→2
0→1
到達可能
5/92 engine detections
View source4 community references
View sourceNo threat flag
View sourceditybit.us
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
ditybit.us
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 ↗
ditybit.us)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.