VirusTotal
6 / 89 engine detections
Open reportkrakenpipeline.com is a Kraken impersonation page detected by PhishDestroy on 2026-08-31. Risk: critical (95/100). Registrar: DonDominio (SCIP). Status: Last known active. Hosting: DigitalOcean, LLC. PhishDestroy sent 1 abuse report. VirusTotal: 6/89 engines flag it. Do not enter credentials or connect a wallet.
“Kraken Pipeline”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@scip.es.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
6 / 89 engine detections
Open report1 threat-system alert
Open report4 community references
Open reportprovider verdict: clean
Open report80/100
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | krakenpipeline.com |
malicious | Sinkholed |
PhishDestroy threat report
krakenpipeline.com is a phishing site that borrows the Kraken exchange brand and presents itself under the page title 'Kraken Pipeline'. It targets Kraken customers and crypto holders who expect a genuine Kraken service. PhishDestroy first flagged it on 2026-08-31, and the page was still online with live content when last checked on 2026-10-19.
The 'Kraken Pipeline' name dresses the site up as an official Kraken product or programme, which gives visitors a reason to trust it and act quickly. Impersonation pages like this usually ask victims to sign in with their exchange credentials and 2FA codes, connect a wallet, or send funds to unlock a promised feature. Anything entered goes straight to the operators. Stolen logins let them empty exchange balances, and wallet connections or deposits move crypto out of the victim's control for good.
Detection coverage is thin. VirusTotal shows 6 of 89 engines flagging the domain as of 2026-09-12: alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. Most scanners still treat the site as clean, so a lack of browser warnings means little here. Wallet-focused defences have caught it, though. MetaMask and SEAL list the domain alongside PhishDestroy, and it appears in 4 AlienVault OTX threat pulses.
The domain was registered on 2024-10-28 through DonDominio (SCIP), almost two years before PhishDestroy detected it. That gap suggests a domain held in reserve or reused rather than one spun up for a single campaign. The site runs on DigitalOcean cloud hosting in the United Kingdom. Its Let's Encrypt certificate gives it the usual browser padlock, which proves nothing about who runs the site.
If you entered Kraken credentials here, change your Kraken password at once, reset 2FA, review active sessions and API keys, and check your withdrawal address whitelist. If you connected a wallet or signed anything, revoke token approvals with a trusted approval checker and move remaining assets to a fresh wallet if you signed a suspicious message. If you sent funds, contact Kraken support and report the theft to authorities with the transaction details. Kraken does not offer a 'Pipeline' service through this domain. Defenders should block krakenpipeline.com at DNS and proxy level and add it to phishing filters, because most commercial engines do not yet catch it.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a056c8-71e1-73ca-a7a5-1dc03a43faae |
|---|---|
| Final url | https://krakenpipeline.com/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://krakenpipeline.com/",
"from": "http://krakenpipeline.com/",
"status": 307
}
] |
| Ip | 134.209.26.210 |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.163.94",
"142.251.179.95",
"134.209.26.210"
] |
| Asns | [
"15169",
"14061"
] |
| Countries | [
"US",
"GB"
] |
| Document hash | 4151d049f2a592a36dd68cb5982d4ce949088062a07245436a582564e3ab479c |
| Globals | [
"ontouchcancel",
"ontouchend",
"ontouchmove",
"ontouchstart",
"animateViewBox",
"svgElement",
"viewBoxX",
"viewBoxY",
"viewBoxX2",
"viewBoxY2",
"incrementX",
"incrementY"
] |
| Tls | {
"san": [
"krakenpipeline.com"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "krakenpipeline.com",
"protocol": "TLS 1.3",
"valid_to": "2026-11-18T01:33:24Z",
"valid_from": "2026-08-20T01:33:25Z"
} |
| Domain age days | 671 |
| Apex age days | 671 |
| Tls age days | 11 |
| Tls valid days | 89 |
| Requests | 6 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 96,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx/1.24.0 (Ubuntu)",
"content-type": "text/html; charset=utf-8",
"x-powered-by": "Express"
} |
Observed: · Retrieved:
| Uuid | cbb0cd5f-f177-432f-aaab-0debf7610785 |
|---|---|
| Final url | https://krakenpipeline.com/ |
| Status | 200 |
| History | [
{
"url": "https://krakenpipeline.com/",
"status": 200
}
] |
| DOM structure hash | 69d4b889c3ba3003ce5c6c0404d5a7d209bf1ff077d21f92e1b32e5dfc4b00a6 |
| Document hash | 4151d049f2a592a36dd68cb5982d4ce949088062a07245436a582564e3ab479c |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "krakenpipeline.com",
"type": "A",
"value": "134.209.26.210"
}
] |
| Dnssec valid | false |
| Ip | 134.209.26.210 |
| Registration record | {
"registrar": "Soluciones Corporativas IP, SL",
"created": "2024-10-28T09:24:02Z",
"updated": "2025-10-24T08:08:33Z",
"expires": "2026-10-28T09:24:02Z",
"nameservers": [
"ns1.dondominio.com",
"ns2.dondominio.com"
]
} |
No. PhishDestroy classifies krakenpipeline.com as a Kraken impersonation page (risk: critical, 95/100); it was first detected on 2026-08-31. VirusTotal: 6/89 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on krakenpipeline.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
Last checked
ns1.dondominio.comns2.dondominio.commx01.dondominio.compriority 10Location describes the IP network.
71aaadc3e7518944f868205d9a34b93b4a8f430bbe649319a117c6cc077952a3krakenpipeline.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of krakenpipeline.com · checked Aug 31, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
krakenpipeline.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
Reachable
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePD-20260831-8C0915
krakenpipeline.com
View sourcePage captured
View source114 stored lookalike domains
Showing 100 of 114
PD-20260831-8C0915 Recipient: abuse@scip.es If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
krakenpipeline.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.