Analysis of the domain kite.claims shows it was actively used as a crypto‑drainer site targeting BitGet users. The site presented the page title “Kite Foundation”, but no SSL certificate was observed, indicating unencrypted HTTP connections. DNS resolution points to the IP address 172.67.209.116, which belongs to Cloudflare’s network (AS13335, United States). The domain is registered through Cloudflare, Inc., and uses the nameservers anirban.ns.cloudflare.com and cass.ns.cloudflare.com, a typical configuration for fast‑flux or proxy‑based abuse. VirusTotal records indicate that 15 of 95 scanned security vendors flagged the domain, and the domain appears on a single external blocklist.
It has been blocked by the PhishDestroy service and carries a Gridinsoft trust score of 0 / 100, reflecting a high likelihood of malicious intent. The malicious payload is identified as the Angel Drainer kit, which is commonly employed to harvest cryptocurrency wallet seeds. The campaign impersonates the BitGet exchange, as indicated by the brand target field, and the scam type is classified as wallet/seed phishing. The domain is currently offline, which may be a temporary takedown or a shift to a new command‑and‑control point.
Defenders should continue to monitor the IP address and associated Cloudflare nameservers for re‑use, enforce blocklisting of the domain and its IP in perimeter defenses, and add the observed indicators (page title, Angel Drainer tag, Gridinsoft score) to threat‑intel feeds. Users of BitGet should be warned about unsolicited requests for seed phrases and instructed to verify URLs via official channels. Because the site lacked TLS, any credentials submitted would have been exposed in clear text, underscoring the need for strict transport security policies. Until further activity is observed, the domain should be treated as high‑risk and remain in blocklists.
집계 기준
처음 저장된 악용사례 신고부터 콘텐츠를 사용할 수 없다는 첫 번째 관찰까지의 경과 시간입니다. 이것은 원인을 확립하지 못합니다.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2025년 11월 2일
DOM Analysisanalyzed 2026년 4월 23일score 20/1008 brand signals
Submitted URLhttp://kite.claims/
ICANN OVERSIGHT
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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:09:00 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-06-17 16:23:52 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 16:23:52 UTC → 2026-09-30 16:14:55 UTC · 2,519.85hmidpoint estimate ≈ 2026-08-09 04:19:23 UTC · precision very 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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='kite.claims', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
kite.claims
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
회복 사기꾼들을 조심하세요! 범죄자는 수사관, 변호사, 회복요원인 척 하면서 피해자에게 다시 연락할 수도 있습니다. 선불 비용을 지불하거나 자격 증명을 공유하지 마십시오. 합법적인 서비스는 도난당한 암호화폐의 복구를 보장할 수 없습니다. 회복 관련 사기에 대해 자세히 알아보기 →
귀하의 암호화폐 거래소 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
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.
암호화폐 사기는 일반적으로 어떻게 이루어지나요?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
악의적인 승인 — 공격자에게 무제한 토큰 사용 권한을 부여하는 “connect wallet” 프롬프트
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로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
하드웨어 지갑을 사용하세요 (Ledger, Trezor). 브라우저 지갑에는 절대 많은 금액을 보관하지 마세요
공식 사이트 즐겨찾기 추가 — 이메일, 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)
