The domain hehrehhrhey.digital was a high-risk crypto drainer phishing site impersonating WalletConnect and using the 'Wallet Connect Abuse' drainer kit. Crypto drainers automatically siphon cryptocurrency from connected wallets by exploiting malicious smart-contract approvals. This site is currently taken offline, but it was actively targeting users seeking WalletConnect services to steal funds without authorization.
Hehrehhrhey.digital was flagged by 3 of 95 VirusTotal security vendors, including CRDF, Ermes, and Gridinsoft, which assigned it a trust score of 0/100. It appeared on 1 security blocklist (PhishDestroy) but was not flagged by Google Safe Browsing. The domain was registered on 2025-07-14 through PDR Ltd. d/b/a PublicDomainRegistry.com and resolved to IP address 172.67.136.157, hosted on Cloudflare (AS13335) in the US. No SSL certificate was available, and the observed page title was 'AMLbot'. The domain used a single nameserver and was classified as a cryptocurrency scam.
Users who interacted with hehrehhrhey.digital should immediately revoke all token approvals using a tool like Etherscan's Token Approval Checker or Revoke.cash. Transfer remaining funds to a new, secure wallet and monitor transaction history for unauthorized activity. Report the domain to platforms such as Google Safe Browsing, PhishTank, or the Anti-Phishing Working Group (APWG) to help prevent further attacks. Enable two-factor authentication on all accounts and remain vigilant for signs of fraud or identity theft.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='hehrehhrhey.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
DOM Analysisanalyzed 2026年4月23日score 81/1001 brand signal
Submitted URLhttps://hehrehhrhey.digital/
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-11 01:08:54 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-28 22:05:45 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-28 22:05:45 UTC → 2026-09-30 16:14:55 UTC · 2,994.15hmidpoint estimate ≈ 2026-07-30 07:10:20 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
あなたの仮想通貨取引所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
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
(IN)
