VirusTotal
2 / 91
“CFT.Report — Комплексная проверка кошельков”
2 / 91
2 threat-system alerts
Reportchecked — no match recorded
23 community references
Reportprovider verdict: clean
Reportstored report
ReportAnalysis completed
Report14 checked — no blocks
Checked; no threat flag recorded
Report| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | cft.report |
malicious | Sinkholed |
| DNS4EU | cft.report |
malicious | Sinkholed |
This domain is flagged as an elevated-risk crypto wallet drainer phishing site targeting Russian-speaking users. Analysis of the infrastructure indicates it was designed to mimic legitimate wallet verification services, likely to siphon cryptocurrency from victims under the guise of a "comprehensive wallet check." Infrastructure analysis reveals the domain cft.report was registered on March 14, 2026, through HOSTINGER operations, UAB, and resolved to the IP address 87.236.16.177. It is currently blocked by two security blocklists and flagged by 4 out of 95 security vendors on VirusTotal. The site employed PHP, Vue.js, Nginx, and third-party libraries such as Unpkg, jsDelivr, and FingerprintJS, which are commonly abused to facilitate client-side attacks. The SSL certificate was issued by Let's Encrypt, a low-friction provider often leveraged by malicious actors to lend superficial legitimacy. The page title, "CFT.Report — Комплексная проверка кошельков," directly translates to a service offering wallet verification, a known pretext for crypto drainer schemes. Mitigation against this threat type requires heightened vigilance when interacting with wallet verification prompts. Users should avoid connecting wallets to unverified platforms, particularly those advertised via unsolicited links or social engineering. Browser-based security extensions that block known malicious domains should be enabled, and wallet software should be configured to require explicit confirmation for high-risk transactions. Organizations should update blocklists to include this domain and its associated IP, while monitoring for similar infrastructure patterns, such as domains registered through the same registrar or resolving to the same hosting provider. Given the domain's current offline status, further monitoring is advised to detect potential re-emergence under a different name or IP.
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
content_divergencehcdnScanner note: alive_content: raw=ok; http=200; via=http_proxy; server=hcdn
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.
ns1.beget.comLocation describes the IP network.
b0cc60965bd308717fee82e7f0bd79225893a7fa9307d41dab2d68379cf712b0www.cft.reportSaved 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 cft.report · checked Jun 26, 2026
9 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.
Reported by 1 community member, first seen Mar 14, 2026
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