Analysis of stealth-hash.support indicates that the domain was registered on 12 October 2025 through Hostinger operations, UAB and is currently taken offline. The site resolved to the IPv6 address 2a02:4780:4c:1604:fb4f:1e7d:cbc9:77b1, which is assigned to AS47583 Hostinger International Limited and geolocated to the United States. No TLS certificate was observed, meaning the site operated without HTTPS. The page title returned by the server was “StealthHash - Cryptocurrency Crime Fighters,” and the domain explicitly impersonates the Ethereum brand, aligning with the reported wallet/seed phishing campaign. Reputation data show that the domain appears on a single security blocklist and is referenced in one AlienVault OTX pulse.
VirusTotal scans recorded seven detections out of ninety‑three security vendors, confirming that multiple scanners flagged the domain as malicious. Independent anti‑phishing services such as PhishDestroy have also blocked the domain, and Gridinsoft assigned a trust score of 0 out of 100, indicating a complete lack of credibility. The authoritative nameservers are ns1.dns-parking.com and ns2.dns-parking.com, both typical of parked or low‑cost hosting services. While the offline status limits immediate observation of the payload or credential‑harvesting mechanisms, the combination of brand impersonation, wallet/seed phishing classification, and the observed detections strongly suggests a malicious intent to harvest cryptocurrency private keys or seed phrases from unsuspecting Ethereum users.
The lack of SSL further reduces the trustworthiness of the site and may facilitate man‑in‑the‑middle interception of submitted data. Defenders should continue to block the IPv6 address and the domain at network perimeter devices, update URL filtering and threat‑intel feeds with the domain and its associated IP, and monitor for any resurgence of the domain or similar patterns hosted on Hostinger infrastructure.
Extracted from stored page analysis
Observed indicators
12 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年4月23日score 100/1006 brand signals
IoC Extractionscanned 2026年8月2日12 wallet · 0 Telegram IoCs
Submitted URLhttp://stealth-hash.support/
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:10:04 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-14 16:48:06 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-14 16:48:06 UTC → 2026-09-30 16:14:55 UTC · 2,591.45hmidpoint estimate ≈ 2026-08-07 16:31:30 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='stealth-hash.support', port=80): Max retries exceeded with url: / (Caused by NewConnection
stealth-hash.support
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(LT)
