This domain, walletverificationservice.online, is identified as a crypto_drainer, a type of malicious infrastructure designed to siphon cryptocurrency from victim wallets through deceptive transaction prompts or wallet-draining scripts. No legitimate brand association is detected, and analysis suggests the use of a generic drainer kit, likely distributed through phishing campaigns or compromised web properties. The domain exhibits no overt branding but operates as a backend service for unauthorized fund transfers. Infrastructure analysis reveals the following technical indicators: the domain resolves to IP address 92.113.23.146 and was registered on March 28, 2026, via HOSTINGER operations, UAB. VirusTotal reports 6 out of 95 security vendors flagging the domain as malicious. It appears on one security blocklist and is referenced in a single AlienVault OTX threat intelligence pulse. The domain is not currently listed in Google Safe Browsing (GSB) at the time of analysis, though this may reflect detection latency rather than benign status. As of the latest assessment, walletverificationservice.online has been taken offline, reducing immediate exposure risk. However, the infrastructure may re-emerge under a different domain or IP. Response actions should include monitoring for related indicators of compromise (IOCs), such as the associated IP and registrant details. Remaining risk is classified as elevated due to the domain's prior functionality as a crypto_drainer, which could resume if the threat actor reactivates the infrastructure. Network defenders are advised to block the domain and IP, and cryptocurrency users should verify transaction prompts independently of any web-based verification services.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='walletverificationservice.online', port=80): Max retries exceeded with url: / (Caused by N
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:10:47 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-04-21 14:35:57 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-21 14:35:57 UTC → 2026-09-30 16:14:55 UTC · 3,889.65hmidpoint estimate ≈ 2026-07-11 15:25:26 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.
VirusTotal Detections Update2026-06-26 10:23:25 UTC
VirusTotal scanner detections updated from 6 to 6. Added scanner alerts: Gridinsoft, SOCRadar, Sophos, alphaMountain.ai.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
13 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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
