VirusTotal
13 / 92 engine detections
レポートを開く“Официальное зеркало Kraken Onion через Tor. Безопасный вход.”
Krakenなりすまし: slon3-kraken-cc.ru — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 13/92 (alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Forcepoint…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 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
slon3-kraken-cc.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 a "secure login", so it targets Russian-speaking users who are searching for a working Kraken entry point. PhishDestroy first flagged the domain on 2026-09-25, and it was still online and serving content as of 2026-10-19.
Fake mirror sites exploit how often Tor services change addresses. Users who search for a current link land on a look-alike page that copies the familiar login screen. Anything typed into it, including usernames, passwords and one-time codes, goes to the operators. They can then take over the real account, empty any balance, or show the victim fake deposit details so new payments go straight to them. The "secure login" wording on this page is part of the lure, not a guarantee.
On 2026-10-07, VirusTotal showed 13 of 92 engines flagging the domain. Among them were BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, Gridinsoft, alphaMountain.ai and the Vietnamese anti-scam project Chong Lua Dao, a spread of independent vendors that reached the same verdict. Spamhaus lists the domain in its DBL under the phishing category, so many mail filters will block it. It also appears in four AlienVault OTX threat pulses alongside the PhishDestroy blocklist entry.
The domain was registered through RU-CENTER on 2026-03-10, about six and a half months before PhishDestroy detected it. That gap suggests a domain held in reserve or kept running quietly before it drew attention. Traffic passes through Cloudflare's network, with the address geolocated to Canada, which hides the real origin server. The padlock comes from a free Let's Encrypt certificate, so it says nothing about who runs the site.
If you entered credentials here, change the password on your real account right away from a source you trust. Reset two-factor authentication and review recent logins, withdrawals and saved payout addresses. Do not send any "deposit" or "verification" payment requested through this page, and treat any address it showed you as belonging to the scammers. Reuse of that password on other services means changing it there too. Defenders should block the domain at DNS, proxy and mail gateways and report it to Cloudflare and the registrar for takedown.
Edge-IP の評判はこのドメインに起因しません。
amos.ns.cloudflare.comkay.ns.cloudflare.comLocation describes the IP network.
76ee12e48f5861fc20b5589653b2e4b8ae001f299f679c2aa93049fad7234217Saved 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.slon3-kraken-cc.ruDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of slon3-kraken-cc.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.
slon3-kraken-cc.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
12→11
11→12
No threat flag
View source13/92 engine detections
View source4 community references
View sourcePage captured
View sourceslon3-kraken-cc.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 ↗
slon3-kraken-cc.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.