krakendate.com is a phishing domain impersonating Kraken, the cryptocurrency exchange. It targets Kraken account holders and traders who might trust a domain carrying the exchange's name. PhishDestroy first flagged it on 2026-08-18. The site has been offline since 2026-09-16, and as of 2026-10-19 its DNS no longer resolves.
How the scam works
Kraken lookalike domains like this one usually serve a copy of the exchange's sign-in flow. Victims are asked for their email, password and one-time 2FA code. With those, the operator can log into the real account, change security settings and withdraw the balance before the owner notices. The page title showed Cloudflare's "Suspected Phishing" warning rather than Kraken branding, so the domain was already behind Cloudflare's phishing interstitial when scanned. We classify it as Kraken impersonation.
Evidence
8 of 89 VirusTotal engines flagged the domain as of 2026-09-17: ChainPatrol, alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, G-Data and SOCRadar. That is a modest count, but it mixes crypto-focused and mainstream security vendors. urlscan.io returned a malicious verdict and detected the Cloudflare warning page. Beyond PhishDestroy, the domain is on the MetaMask and SEAL blocklists, and it appears in 3 AlienVault OTX threat pulses.
Infrastructure
The domain is registered through Spaceship, Inc. with a registration date of 2026-09-08, which is later than PhishDestroy's first sighting on 2026-08-18. It sat behind Cloudflare's network in the US, so the address it resolved to belonged to Cloudflare's proxy, not the operator's actual server. It went dark on 2026-09-16, about a month after first detection.
What to do
If you entered Kraken credentials on this domain, sign in to Kraken directly and change your password at once. Reset your 2FA, review active sessions and API keys, and check withdrawal addresses and recent activity for anything you did not authorize. Change the same password anywhere else you reused it. Contact Kraken support if funds moved or settings changed. Defenders should block the domain and watch for new Kraken-themed registrations with similar wording.
집계 기준
처음 저장된 악용사례 신고부터 콘텐츠를 사용할 수 없다는 첫 번째 관찰까지의 경과 시간입니다. 이것은 원인을 확립하지 못합니다.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2026년 8월 18일
Observed page title
Suspected Phishing | Cloudflare
Automated brand references
Kraken
TLS 인증서
발급자 WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.171.16
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
네임서버 1
launch2.spaceship.net
Location describes the IP network.
TLS 인증서
Issuer
WE1
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-19 01:14:00 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-09-08 12:28:39 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-08 12:28:39 UTC → 2026-09-30 16:14:55 UTC · 531.77hmidpoint estimate ≈ 2026-09-19 14:21:47 UTC · precision low · basis bounded
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.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
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.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
FBI 지침
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 krakendate.com)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
지역 경찰 — 비록 당장 조치를 취할 수는 없더라도 공식 기록을 남깁니다
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?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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.
(US)
