VirusTotal
6 / 92 engine detections
レポートを開く“Официальное зеркало Kraken Onion через Tor. Безопасный вход.”
Krakenなりすまし: slon-kraken.ru — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 6/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 92 engine detections
レポートを開くDBL_PHISH
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-kraken.ru is an impersonation phishing page that borrows the Kraken name and presents itself, in Russian, as "the official mirror of Kraken Onion via Tor" with a "secure login." It targets Russian-speaking users looking for a working way into a Kraken account without opening the Tor Browser. PhishDestroy first flagged the domain on 2026-09-24. As of 2026-10-19 the site was still online and serving its content.
The page title promises an "official mirror" and "secure login," a pitch aimed at people who expect mirror domains to rotate and so cannot easily tell a real one from a fake. A lookalike mirror like this shows a familiar login form. Whatever the visitor types, including username, password and often a one-time code, goes to the operators, who can then sign in to the real account and take its balance. Deposit addresses shown on a fake mirror are also controlled by the scammers, so any funds sent there are gone.
On 2026-10-07, 6 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That is a modest share, so many browsers and security tools will still load the page without a warning. Spamhaus lists the domain in its DBL as phishing, and it appears in four AlienVault OTX threat pulses, so several independent sources back the classification. PhishDestroy lists it on its own blocklist.
The domain was registered through RU-CENTER on 2026-03-26, about six months before PhishDestroy detected it. That gap suggests it was set up well ahead of use or ran for some time before anyone flagged it. Traffic is served through Cloudflare, with the visible address geolocating to Canada. That address belongs to Cloudflare's edge network, so it hides where the page is actually hosted.
Do not log in through slon-kraken.ru or any "mirror" link that reached you through search results, chats or forums. If you entered credentials there, change the password right away from a trusted access point, reset two-factor authentication, end all active sessions, and check for unfamiliar withdrawals or new withdrawal addresses. Never send funds to an address displayed on this page. Defenders should block the domain at DNS and proxy level, report it to Cloudflare and the registrar, and watch for sibling domains built on the same "kraken mirror" naming pattern.
Edge-IP の評判はこのドメインに起因しません。
amos.ns.cloudflare.comkay.ns.cloudflare.comLocation describes the IP network.
20c50485488bc8d428770d4bf2b91835291d8b126e650885d0a4c4d71ba7a93cSaved 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 slon-kraken.ru · checked Sep 24, 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-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
4→5
5→4
4→5
3→4
2→3
到達可能
No threat flag
View source6/92 engine detections
View source4 community references
View sourcePage captured
View sourceslon-kraken.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 ↗
slon-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.