VirusTotal
20 / 89
“imToken | Ethereum & Bitcoin Wallet”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@v-sys.org.
The latest stored availability evidence still shows the domain reachable; 2 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | mtoken-im.cv |
malicious | Sinkholed |
| DigiCert UltraDNS | mtoken-im.cv |
malicious | Sinkholed |
| DNS4EU | mtoken-im.cv |
malicious | Sinkholed |
This domain, mtoken-im.cv, was registered through the Gname registrar on July 28 2026 and is currently active. DNS resolution points to the single IPv4 address 176.97.124.73, served by the authoritative name servers a.share-dns.com, a1.share-dns.com, b.share-dns.net, and b1.share-dns.net. The domain appears on two public security blocklists and is actively listed by PhishDestroy and OpenPhish, indicating that the infrastructure is already recognized as malicious. VirusTotal reports that 17 of 91 scanning engines have flagged the domain, providing additional confirmation of its suspicious nature.
No public page title, SSL certificate details, or HTTP response codes have been disclosed, so the exact content and delivery mechanisms remain unknown. The lack of visible brand references or a known phishing kit prevents attribution to a specific campaign, but the classification as a generic phishing operation is supported by the blocklist entries. Defenders should prioritize immediate containment: add mtoken-im.cv and its resolving IP 176.97.124.73 to perimeter deny lists, enforce DNS sinkholing, and ensure that email gateways block any messages containing the domain.
Continuous monitoring of DNS queries for the four name servers can reveal additional infrastructure expansions. Because the domain is newly created, threat actors may still be testing delivery vectors; therefore, security teams should also watch for new variants that reuse the same name servers or IP range. Incident response teams should collect any observed traffic logs that reference the domain for deeper forensic analysis, and threat‑intel feeds should be updated to reflect the current detection counts and blocklist status.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='mtoken-im.cv', port=80): Read timed out. (read timeout=7)
a.share-dns.coma1.share-dns.comb.share-dns.netb1.share-dns.netLocation describes the IP network.
2dd8600a6481b6746500f32c1023a35411a5f6a4806260b0c6e96e5e0adf3958Saved 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 mtoken-im.cv · checked Aug 1, 2026
176.97.124.73. 15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
52 stored lookalike domains
PD-20260801-082241 Recipient: abuse@v-sys.org Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive