VirusTotal
5 / 91 engine detections
打开报告“Официальное зеркало Kraken Onion через Tor. Безопасный вход.”
冒充 Kraken: zerkalo-kraken-onion.ru — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 5/91 (CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar, VIPRE); PhishDestroy…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
5 / 91 engine detections
打开报告4 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
zerkalo-kraken-onion.ru is an impersonation phishing page that poses as an official "mirror" of Kraken reached through Tor. Its Russian-language title promises a safe entry point: "Официальное зеркало Kraken Onion через Tor. Безопасный вход." (Official Kraken Onion mirror via Tor. Secure login.) The page targets Russian-speaking users who search for a working Kraken link. PhishDestroy first saw it on 2026-09-25, and it was still online and serving content on 2026-10-19.
Fake mirror sites work because users expect onion services to change addresses and go looking for the current "official" link. A page like this copies the brand's look and offers a login form. Anything typed into it, such as usernames, passwords and one-time codes, goes straight to the operators. With those details they can take over the real account and drain its balance. The promise of a "secure login" is part of the bait, not a sign of safety.
On 2026-10-06, 5 of 91 VirusTotal engines flagged the domain: CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That is a low detection rate, so many browsers and security tools will still let the page load without a warning. The domain appears in four AlienVault OTX threat pulses, which means other researchers have tied it to malicious activity. PhishDestroy lists it on our blocklist.
The domain was registered on 2026-04-08 through RU-CENTER-RU, roughly five and a half months before we detected it. That gap suggests it was set up in advance rather than spun up for a quick hit. Traffic runs through Cloudflare, Inc. (an edge address geolocated to Canada), which hides the server where the page actually lives. Its Let's Encrypt certificate gives it the padlock icon, but that only means the connection is encrypted, not that the site is legitimate.
If you entered credentials on this page, log in through a link you have verified independently and change your password at once. Use a new password that you have not used anywhere else. Reset two-factor authentication and review active sessions and withdrawal settings for changes you did not make. Treat any "mirror" link from search results or chats as hostile until you have checked it against a trusted source. Defenders should block the domain at DNS and the proxy, and add it to phishing filters, since few vendors detect it yet.
Edge-IP 声誉不属于此域。
arch.ns.cloudflare.comeve.ns.cloudflare.comLocation describes the IP network.
8f04bbc7627ab418227a59c4ce5a5c1fe15711b4259e4e1fbe8242020b5114b5Saved 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 zerkalo-kraken-onion.ru · checked Sep 25, 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.
zerkalo-kraken-onion.ru
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
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
2→3
1→2
0→1
可访问
No threat flag
View source5/91 engine detections
View source4 community references
View sourcePage captured
View sourcezerkalo-kraken-onion.ru
View source已存储 114 个仿冒域名
显示 114 个中的 100 个
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 ↗
zerkalo-kraken-onion.ru)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.