This domain is flagged as an elevated-risk crypto drainer phishing operation targeting onchain asset management users. Analysis indicates the site was designed to mimic legitimate decentralized finance platforms, likely to execute unauthorized transactions or drain cryptocurrency wallets upon interaction. The specific threat type—crypto drainer—is characterized by its focus on extracting digital assets through deceptive smart contract interactions or wallet connection prompts, a growing vector in financial fraud. Infrastructure analysis reveals multiple high-confidence indicators of compromise. The domain kpk.capital was registered on October 30, 2024, through HOSTINGER operations, UAB, a registrar frequently associated with short-lived phishing domains. It resolves to the IP address 188.114.96.3, which has been linked to other malicious infrastructure in recent threat intelligence reports. Security vendors on VirusTotal flagged the domain at a 4/95 detection rate, while it appears on three distinct security blocklists, including those maintained by browser extensions and enterprise security platforms. AlienVault OTX records the domain in two threat intelligence pulses, further corroborating its malicious classification. The page title, 'KPK | Scalable onchain asset management,' aligns with common phishing tactics that leverage cryptocurrency-related terminology to establish false credibility. Mitigation steps for this threat type require immediate action from both end users and security teams. Users who interacted with kpk.capital should revoke any connected wallet permissions via blockchain explorers or dedicated revocation tools, as crypto drainers often exploit lingering smart contract authorizations. Wallet addresses associated with the domain should be treated as compromised and added to internal blocklists. Organizations should update firewall rules to block the domain and its resolving IP (188.114.96.3) at the network perimeter. Given the domain's recent creation date and registrar history, security teams should monitor for newly registered domains under the same registrar or IP range, as threat actors frequently rotate infrastructure. For users, verifying domain authenticity through official project documentation or community channels remains critical to avoiding similar phishing schemes.
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:01 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-17 22:18:58 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 22:18:58 UTC → 2026-09-30 16:14:55 UTC · 2,513.93hmidpoint estimate ≈ 2026-08-09 07:16:56 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.
Last analyzed First positive detection Previous stored snapshot: 4 detections
ChainPatrol
alphaMountain.ai
Forcepoint ThreatSeeker
SOCRadar
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
2513.93
Estimate basis
Bounded by observations
Estimate precision
very_low
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='kpk.capital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
kpk.capital
保存済みの結果
到達不能
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
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.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
