kraken-zerkalocc.ru is a Kraken impersonation page detected by PhishDestroy on 2026-09-25. Risk: critical (88/100). Registrar: SELECTEL-RU. Status: Reachable · access restricted. Hosting: Cloudflare, Inc. VirusTotal: 5/91 engines flag it. Do not enter credentials or connect a wallet.
kraken-zerkalocc.ru poses as a "mirror" of Kraken. "Zerkalo" is Russian for mirror, a word used to pass off clones as official backup addresses. The site targets people searching for an alternate way into Kraken and greets them with a page titled "Authorization." PhishDestroy first flagged it on 2026-09-25, and it was still online and serving content when checked on 2026-10-19.
How the scam works
Mirror scams depend on users who believe the real site is blocked or unreachable and go looking for a working copy. The visitor lands on what looks like Kraken's sign-in step and enters a username, password and often a one-time 2FA code. Those details go to the operators, who can use them to log into the genuine account, move funds or resell access. Nothing on the clone itself needs to work, because the theft is complete once the form is submitted.
Evidence
Five of 91 VirusTotal engines flagged the domain as of 2026-10-06: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a thin margin. Most security tools still let the page load, so a missing browser warning means little here. The domain also appears in four AlienVault OTX threat pulses, which shows other researchers are tracking it, and it is on the PhishDestroy blocklist.
Infrastructure
The domain was registered through SELECTEL-RU on 2026-01-06, more than eight months before PhishDestroy detected it. That long, quiet lead time lets a domain age past the filters that distrust brand-new registrations. Traffic passes through Cloudflare, Inc. (edge address 188.114.97.3, listed in Canada), so the server actually hosting the page is hidden behind the proxy. The valid certificate from Google Trust Services only means the connection is encrypted. It does not show who runs the site.
What to do
If you typed your Kraken login here, change the password immediately from the official app or a bookmarked address. Then reset 2FA and sign out all active sessions. Review recent logins, withdrawal addresses and API keys, and remove anything you did not create. If you reuse that password elsewhere, change it there too, and contact Kraken support if you see unauthorized activity. Defenders should block the domain and watch for lookalike names that pair Kraken with "zerkalo" or "mirror" wording.
No. PhishDestroy classifies kraken-zerkalocc.ru as a Kraken impersonation page (risk: critical, 88/100); it was first detected on 2026-09-25. VirusTotal: 5/91 engines flag it. Treat the site as unsafe.
Is kraken-zerkalocc.ru safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on kraken-zerkalocc.ru. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used kraken-zerkalocc.ru?
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.
RegistrationCreated Jan 6, 2026 (289d)—Expires Jan 6, 2027
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedSep 25, 2026
DOM Analysisanalyzed Oct 9, 2026score 88/100
Submitted URLhttps://kraken-zerkalocc.ru/
Favicon Hash
Observed page title
Authorization
TLS Certificate
Issued by Google Trust Services / WE1· stored validity ends in 37 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
kyree.ns.cloudflare.com
lucy.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-08-31 06:01:48
Valid until
2026-11-29 07:01:45
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 04:03:41 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta1b7bff4d3f9cf3eab2d64a053eb97cdb9932fc337ace4d54e2ec6574ab9b556Certificate names · 2 SANs
kraken-zerkalocc.ru
*.kraken-zerkalocc.ru
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Captcha85% confidence
Attributionmechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCaptchaChallenge85%2026-10-22 10:29:29 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:29:29 UTClast content: 2026-10-21 22:32:31 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 4 identified
H
HSTS
Security
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · kraken-zerkalocc.ru
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches8
Same favicon hash or the same page title as this host.
4 evidence signal groups linked0 stored notification recordsReachable · access restricted
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including kraken-zerkalocc.ru)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
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.
