VirusTotal
2 / 91 engine detections
Відкрити звіт“CFT.Report — Комплексная проверка кошельков”
домен у блоклистах: cft.report — Прикритий · доступний (HTTP 200). Зведення доказів: VirusTotal 2/91 (alphaMountain.ai, Gridinsoft); URLQuery 2 alerts; 1…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
2 / 91 engine detections
Відкрити звіт2 threat-system alerts
Відкрити звітchecked — no match recorded
23 community references
Відкрити звітprovider verdict: clean
Відкрити звіт14 перевірено — блокувань немає
No threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | cft.report |
malicious | Sinkholed |
| DNS4EU | cft.report |
malicious | Sinkholed |
PhishDestroy threat report
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.
Last checked
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.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.cft.reportDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of cft.report · checked Jun 26, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
content_divergence · alive_content: raw=ok; http=200; via=http_proxy; server=hcdn
cft.report
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
4→4
23 community references
View source2/91 engine detections
View sourceNo threat flag
View sourcePage captured
View sourcecft.report
View sourceПовідомив 1 учасник спільноти; уперше помічено 14.03.2026
Listed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
cft.report)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.