VirusTotal
6 / 90 engine detections
レポートを開くフィッシング: hjmnbld.xyz — コンテンツが利用できません. 証拠の概要: VirusTotal 6/90 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, G-Data, Gridinsoft); 1 external blocklist…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 90 engine detections
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開く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
hjmnbld.xyz was an impersonation phishing page that passed itself off as a legitimate service to win the trust of crypto users. PhishDestroy first detected it on 2026-08-26. The site has been offline since 2026-09-11, and it was still dead with no reachable content at the last check on 2026-10-19. Its run was short, just over two weeks from first detection to going dark, but the domain should still be treated as hostile in case it returns.
Impersonation pages copy the look, wording and flow of a brand people already trust, then wait for visitors arriving from ads, direct messages, fake support replies or search results. Once the visitor believes they are on the real service, the page asks them to log in, enter a recovery phrase, or connect a wallet and sign a request. Each of these hands control to the operator: a seed phrase gives full access to the wallet, a signed approval lets the attacker move tokens, and a password opens the account. Losses are usually immediate and cannot be reversed.
Six of 90 VirusTotal engines flagged the domain as of 2026-09-05: alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, G-Data, Gridinsoft and SOCRadar. That count is modest, but these are independent vendors reaching the same verdict, which is typical for a fresh phishing domain caught early. ScamSniffer, a crypto-focused scam feed, lists it alongside PhishDestroy. The domain also appears in four AlienVault OTX threat pulses, so it is already being shared among researchers.
The domain was registered through NameCheap, Inc. on the low-cost .xyz extension. Its name is a meaningless string of letters with no link to any real brand, which points to a disposable domain meant to survive only until it was blocked. The roughly 16 days between first detection and going offline fits that throwaway pattern.
If you entered a seed phrase or private key on this site, assume the wallet is compromised: create a new wallet on a trusted device and move any remaining funds there right away. If you connected a wallet or signed anything, check your token approvals with a reputable revocation tool and revoke unfamiliar ones. If you typed a password, change it everywhere you reuse it and turn on app-based 2FA. Defenders should block hjmnbld.xyz at DNS and proxy level, search logs for past visits, and watch for lookalike random-string .xyz domains used in the same campaigns.
Last checked
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
dns2.registrar-servers.comeforward3.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward1.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20An 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.
hjmnbld.xyz
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
利用不可→到達可能
到達可能→利用不可
到達可能
6/90 engine detections
View source4 community references
View sourceNo threat flag
View sourcehjmnbld.xyz
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 ↗
hjmnbld.xyz)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.