Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
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.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note: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
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Oct 30, 2024 —Expires Oct 30, 2027
Time to First Unavailability2h
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedMay 28, 2026
DOM Analysisanalyzed Jun 11, 2026score 68/100
Submitted URLhttp://kpk.capital/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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 inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:09:06 UTC
RDAP registrationUnknown
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
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-06-26 02:27:23 UTC
VirusTotal scanner detections updated from 0 to 4. Added scanner alerts: ChainPatrol, Forcepoint ThreatSeeker, SOCRadar, alphaMountain.ai.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
4 detections recorded on VirusTotal — vendor total unavailable
Jun 26, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 11, 2026
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Jun 11, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
May 28, 2026
Time to First Unavailability
2 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
6 evidence signal groups linked1 reports recordedContent unavailable
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · kpk.capital
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.
