VirusTotal
13 / 92 engine detections
レポートを開く“Официальное зеркало Kraken Onion через Tor. Безопасный вход.”
Krakenなりすまし: slon-to-kraken.ru — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 13/92 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 92 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
slon-to-kraken.ru is an impersonation phishing page built around the Kraken name. Its Russian-language title promises an "official mirror of Kraken Onion via Tor" with "secure login," so it is aimed at Russian-speaking users looking for a working Kraken entry point. PhishDestroy first flagged it on 2026-09-25. As of 2026-10-19 the site was still online and serving its content.
Fake mirror sites exploit people who cannot reach the service they want directly and go searching for an alternative address. The page imitates the expected login screen, and whatever username, password or one-time code the visitor types goes straight to the operators. With those credentials they can take over the real account, change payout details and empty its balance. Some mirrors also display their own deposit addresses, so any cryptocurrency "topped up" through the page lands in the scammers' wallets and cannot be recovered.
On 2026-10-07, 13 of 92 VirusTotal engines flagged the domain, including BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, Lionic and alphaMountain.ai. That is a minority of engines, but the names come from several independent, established vendors. The domain also appears in four AlienVault OTX threat pulses, which shows other researchers are tracking it. PhishDestroy lists it on its own blocklist.
The domain was registered through RU-CENTER on 2026-03-10, about six and a half months before PhishDestroy caught it. That gap suggests a page that stayed in quiet use long before it was detected. Traffic runs through Cloudflare, with the edge address located in Canada, so the actual origin server is hidden. The Let's Encrypt certificate only provides the padlock. It does not make the "secure login" claim true.
If you entered credentials on this page, change your password on the genuine service at once and reset any reused passwords elsewhere. Then enable or re-enroll two-factor authentication and review active sessions and saved withdrawal or payout addresses for changes. Do not send funds to any address the page showed you, and treat any crypto already sent as lost. Defenders should block the domain and watch for lookalike "slon" or "kraken mirror" variants. Takedown reports can go to RU-CENTER and Cloudflare.
Edge-IP の評判はこのドメインに起因しません。
amos.ns.cloudflare.comkay.ns.cloudflare.comLocation describes the IP network.
b50a34f336dd65bbdfd4afc58a2ba8575af77135959af5c61e5137082aa9cbebSaved 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.slon-to-kraken.ruDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of slon-to-kraken.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.
slon-to-kraken.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
11→13
10→11
到達可能
No threat flag
View source13/92 engine detections
View source4 community references
View sourceslon-to-kraken.ru
View sourcePage captured
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 ↗
slon-to-kraken.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
保存されたブロックリスト、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.