VirusTotal
6 / 92 engine detections
Open reportzerkalo-slon-kraken.ru is a Kraken impersonation page detected by PhishDestroy on 2026-09-24. Risk: critical (88/100). Registrar: RU-CENTER-RU. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 6/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“Официальное зеркало Kraken Onion через Tor. Безопасный вход.”
6 / 92 engine detections
Open reportDBL_PHISH
4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
zerkalo-slon-kraken.ru is a phishing page that impersonates Kraken. Its Russian page title, "Официальное зеркало Kraken Onion через Tor. Безопасный вход.", promises an "official Kraken Onion mirror via Tor" with a "secure login". The name itself ("zerkalo" means mirror) targets Russian-speaking users who search the open web for a working Kraken mirror. PhishDestroy first saw the domain on 2026-09-25, and it was still online and serving its content on 2026-10-19.
Mirror-phishing sites rely on users who cannot reach a service directly and go looking for an alternate address. The page copies the look of the Kraken login and stresses safety and Tor access to lower the visitor's guard. Whatever is typed into the form, usually a username, password and sometimes a one-time code, goes to the operators. They can use it to take over the real account and empty its balance. Victims typically lose account access and any funds held there, and some are also pushed to send deposits to addresses the scammers control.
Six of 92 VirusTotal engines flagged the domain as of 2026-10-07: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. Many engines are still silent, but the flags come from several independent vendors. Spamhaus lists the domain in its DBL with a phishing tag (DBL_PHISH), and four AlienVault OTX threat pulses reference it. PhishDestroy carries it on its blocklist.
The domain was registered through RU-CENTER-RU on 2026-03-12, more than six months before PhishDestroy flagged it. That long gap fits a domain that was aged or quietly circulated before it drew attention. It resolves to 188.114.97.3 on Cloudflare's network with a Canadian location. This address belongs to Cloudflare's proxy and does not reveal the real server. The site uses a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether the page is legitimate.
If you entered a login on this page, go to the genuine service through an address you already trust and change your password right away. Change it anywhere else you reused it, enable or reset two-factor authentication, and review recent sessions and withdrawals. Do not send deposits or "verification" payments requested through this site, and never trust mirror links found through search results or chats. Defenders should block the domain at DNS and proxy level and alert on traffic to it. Abuse reports to Cloudflare and RU-CENTER will help get the page taken down.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0d5ac-a8d4-755e-a18a-67c992c561d2 |
|---|---|
| Final url | https://zerkalo-slon-kraken.ru/ |
| Status | 200 |
| Ip | 188.114.96.3 |
| Contacted domains | [
"mc.yandex.com",
"mc.yandex.ru"
] |
| Contacted IP addresses | [
"87.250.251.119",
"188.114.96.3"
] |
| Asns | [
"13238",
"13335"
] |
| Countries | [
"RU"
] |
| Linked domains | [
"xn--sln18-vta.cc",
"krakenu6upk4yrcys6nv25du7ntl7inovhnepkevynfdgkjekkklrgqd.onion"
] |
| Document hash | ec26c182c4234f89194865e3e7a7c38e9410cc5242d0fc3f60cde64c719faacb |
| Script hashes | [
"726ac59577c8aeeec94c61bfb7791a709e401b5d871d35c39a65cd948f6124e3",
"2595496fe48df6fcf9b1bc57c29a744c121eb4dd11566466bc13d2e52e6bbcc8",
"fbe11af6f29f55ae480e2058aad3ac400315d2792c3b14346f016b70cebf3bb3",
"063840b4b3f5869e0f0d078bab8bd29cfb3a59ee85e8e3edbbec35a8fe846fd3"
] |
| Globals | [
"requestResize",
"ym",
"_wpemojiSettings",
"twemoji",
"wp",
"Ya",
"yaCounter112384039",
"dataLayer"
] |
| Cookies | [
"bh",
"_ym_uid",
"_ym_d",
"sync_cookie_csrf",
"_ym_isad",
"_yasc",
"yabs-sid",
"i",
"yandexuid",
"yuidss",
"ymex",
"sync_cookie_csrf_secondary",
"sync_cookie_ok_secondary",
"_ym_visorc"
] |
| Storage keys | [
"wpEmojiSettingsSupports",
"_ymBRC",
"_ym_synced",
"_ym112384039_lsid",
"_ym112384039:0_reqNum",
"_ym_uid",
"_ym_retryReqs",
"_ym_jn"
] |
| Tls | {
"san": [
"*.zerkalo-slon-kraken.ru",
"zerkalo-slon-kraken.ru"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "zerkalo-slon-kraken.ru",
"protocol": "QUIC",
"valid_to": "2026-12-04T11:17:26Z",
"valid_from": "2026-09-05T11:17:27Z"
} |
| Domain age days | 196 |
| Apex age days | 196 |
| Tls age days | 19 |
| Tls valid days | 89 |
| Requests | 46 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 75,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html"
} |
Observed: · Retrieved:
| Uuid | 79ef96ae-3866-4d6a-ad31-9047f6276f34 |
|---|---|
| Final url | https://zerkalo-slon-kraken.ru/ |
| Status | 200 |
| History | [
{
"url": "https://zerkalo-slon-kraken.ru/",
"status": 200
}
] |
| DOM structure hash | 6b0bb1a7e3f0c7e6014d8e8568877f8817fbc5aa023ba2be771fcfecc75d3e6d |
| Document hash | f8480d004c86af0df3fa891702577ebd2c0fe9039d756eea2fad9aa742407e45 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "zerkalo-slon-kraken.ru",
"type": "A",
"value": "188.114.96.0"
},
{
"name": "zerkalo-slon-kraken.ru",
"type": "A",
"value": "188.114.97.0"
},
{
"name": "zerkalo-slon-kraken.ru",
"type": "AAAA",
"value": "2a06:98c1:3120::"
},
{
"name": "zerkalo-slon-kraken.ru",
"type": "AAAA",
"value": "2a06:98c1:3121::"
}
] |
| Dnssec valid | false |
| Ip | 188.114.96.0 |
| Registration record | {
"registrar": "RU-CENTER-RU",
"created": "2026-03-12T06:54:15Z",
"expires": "2027-03-12T06:54:15Z",
"nameservers": [
"amos.ns.cloudflare.com",
"kay.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 53,
"malicious": 4,
"suspicious": 2,
"undetected": 33
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"Fortinet": "spam",
"SOCRadar": "phishing",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"Dr.Web": "drugs",
"alphaMountain.ai": "Phishing (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "phishing and other frauds"
} |
| Created | 2026-03-12T00:00:00Z |
| First seen | 2026-03-12T07:43:04Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "104.21.47.18"
},
{
"ttl": 21600,
"type": "NS",
"value": "amos.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "172.67.143.198"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "amos.ns.cloudflare.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "kay.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3031::ac43:8fc6"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3035::6815:2f12"
}
] |
| Dns at | 2026-10-07T02:05:17Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"*.zerkalo-slon-kraken.ru",
"zerkalo-slon-kraken.ru"
],
"issuer": "Let's Encrypt / YE1",
"serial": "5c04213c891865f47c762c9be6e13eb2ef",
"sha256": "181d20eaf2d56c7cf26a89148c28d6d0c0163c209205cd9ec2be3f5822484a57",
"subject": "zerkalo-slon-kraken.ru",
"valid_to": "2026-12-04T11:17:26Z",
"valid_from": "2026-09-05T11:17:27Z"
} |
No. PhishDestroy classifies zerkalo-slon-kraken.ru as a Kraken impersonation page (risk: critical, 88/100); it was first detected on 2026-09-24. VirusTotal: 6/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on zerkalo-slon-kraken.ru. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Edge-IP reputation is not attributed to this domain.
amos.ns.cloudflare.comkay.ns.cloudflare.comLocation describes the IP network.
181d20eaf2d56c7cf26a89148c28d6d0c0163c209205cd9ec2be3f5822484a57*.zerkalo-slon-kraken.ruzerkalo-slon-kraken.ruSaved 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-slon-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.
zerkalo-slon-kraken.ru
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
5→6
4→5
3→4
Reachable
No threat flag
View source6/92 engine detections
View source4 community references
View sourcePage captured
View sourcezerkalo-slon-kraken.ru
View source114 stored lookalike domains
Showing 100 of 114
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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-slon-kraken.ru)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.