VirusTotal
5 / 91 engine detections
Open reportssilka-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: 5/91 engines flag it. Do not enter credentials or connect a wallet.
“Официальное зеркало Kraken Onion через Tor. Безопасный вход.”
5 / 91 engine detections
Open report4 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
ssilka-kraken.ru is an impersonation phishing page that trades on the Kraken name. The domain is transliterated Russian for "Kraken link," and it is aimed at Russian-speaking users searching for a working Kraken address. PhishDestroy first flagged it on 2026-09-25. As of 2026-10-19 the site was still online and serving its content.
The page title reads "Официальное зеркало Kraken Onion через Tor. Безопасный вход.", which translates to "Official Kraken Onion mirror via Tor. Secure login." Lookalike "mirror" sites like this rely on users who cannot easily verify a link and assume that a search result or a forwarded address is genuine. The visitor is shown a familiar-looking login form or an address to visit next. The username and password typed in go straight to the operators, who can use them to empty the real account. Some of these pages also ask for a deposit, so the money is sent to an address the scammers control.
On 2026-10-06, 5 of 91 VirusTotal engines flagged the domain as malicious: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That count is modest, so many browsers and security tools will still open the page without a warning. The domain appears in four AlienVault OTX threat pulses, which shows other researchers are tracking it. It is listed on the PhishDestroy blocklist.
The domain was registered on 2026-04-20 through RU-CENTER-RU, about five months before PhishDestroy detected it. That gap left it a long window to build search visibility before anyone flagged it. The site sits behind Cloudflare at 188.114.97.3, which geolocates to Canada. That address belongs to Cloudflare's network and reveals nothing about where the real server is located.
If you entered a login on this page, change that password immediately from a link you trust, and change it anywhere else you reused it. Turn on app-based two-factor authentication and review recent logins and withdrawals on the genuine account. Do not send any deposit, and treat any payment already made as lost to the operators. Reach the real service only through a bookmarked or independently verified address, never through a "mirror" from a search result or a chat. Defenders should block ssilka-kraken.ru at DNS and the web proxy and watch for similar transliterated Kraken lookalikes on the .ru zone.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0d5c4-57bb-72f6-b094-2943ca8c5064 |
|---|---|
| Final url | https://ssilka-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 | b175c1d8c9e5e77362917513beb5bcc28028ffeef256419ad151a9c01928b7de |
| 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",
"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": [
"*.ssilka-kraken.ru",
"ssilka-kraken.ru"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "ssilka-kraken.ru",
"protocol": "QUIC",
"valid_to": "2026-11-15T09:22:47Z",
"valid_from": "2026-08-17T09:22:48Z"
} |
| Domain age days | 156 |
| Apex age days | 156 |
| Tls age days | 38 |
| Tls valid days | 89 |
| Requests | 46 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 83,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html"
} |
Observed: · Retrieved:
| Uuid | ccd37062-4fef-4a28-9a64-72b88b83477d |
|---|---|
| Final url | https://ssilka-kraken.ru/ |
| Status | 200 |
| History | [
{
"url": "https://ssilka-kraken.ru/",
"status": 200
}
] |
| DOM structure hash | 237c7b243dad80db458c4aff5eb6a18b57aeaa9044ba9805ccdd2187a959d649 |
| Document hash | 583def483a4525448fb42ebebd089f2312fde8b62c6fb9584cbffe4b4ba258ae |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "ssilka-kraken.ru",
"type": "A",
"value": "172.67.211.202"
},
{
"name": "ssilka-kraken.ru",
"type": "A",
"value": "104.21.75.39"
},
{
"name": "ssilka-kraken.ru",
"type": "AAAA",
"value": "2606:4700:3037::6815:4b27"
},
{
"name": "ssilka-kraken.ru",
"type": "AAAA",
"value": "2606:4700:3033::ac43:d3ca"
}
] |
| Dnssec valid | false |
| Ip | 172.67.211.202 |
| Registration record | {
"registrar": "RU-CENTER-RU",
"created": "2026-04-20T10:53:15Z",
"expires": "2027-04-20T10:53:15Z",
"nameservers": [
"igor.ns.cloudflare.com",
"sloan.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 0,
"suspicious": 0,
"undetected": 37
} |
|---|---|
| Reputation | 0 |
| Created | 2026-04-20T00:00:00Z |
| First seen | 2026-04-21T11:43:32Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "172.67.211.202"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3033::ac43:d3ca"
},
{
"ttl": 21600,
"type": "NS",
"value": "sloan.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3037::6815:4b27"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.75.39"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "igor.ns.cloudflare.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "igor.ns.cloudflare.com"
}
] |
| Dns at | 2026-10-19T13:50:14Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"*.ssilka-kraken.ru",
"ssilka-kraken.ru"
],
"issuer": "Let's Encrypt / YE1",
"serial": "650307eb6c45f159055277f41557161cba3",
"sha256": "375e72d624c2912c4042b6bb5e8cf91522447e5e2e8daabeadd7f4e5de486447",
"subject": "ssilka-kraken.ru",
"valid_to": "2027-01-13T08:47:12Z",
"valid_from": "2026-10-15T08:47:13Z"
} |
No. PhishDestroy classifies ssilka-kraken.ru as a Kraken impersonation page (risk: critical, 88/100); it was first detected on 2026-09-24. VirusTotal: 5/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on ssilka-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.
igor.ns.cloudflare.comsloan.ns.cloudflare.comLocation describes the IP network.
74926d028249ce2e83c96fc6839e66400e3b9bc668f4bcaccdd8ede9377c19c5*.ssilka-kraken.russilka-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 ssilka-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.
ssilka-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
4→3
2→4
1→2
0→1
2→Observation retained
Reachable
No threat flag
View source5/91 engine detections
View source4 community references
View sourcePage captured
View sourcessilka-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 ↗
ssilka-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.