VirusTotal
7 / 91 engine detections
Open reportintark.shop is a Kraken impersonation page detected by PhishDestroy on 2026-09-25. Risk: critical (88/100). Registrar: Registrar.eu. Hosting: VPSPay ASN. PhishDestroy sent 1 abuse report. VirusTotal: 7/91 engines flag it. Do not enter credentials or connect a wallet.
“KrakenSNOS AI — единый интерфейс ко всем моделям”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@registrar.eu.
The latest stored availability evidence still shows the domain reachable; 28 days 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.
7 / 91 engine detections
Open reportSuspicious
Open reportScan report
Open report4 community references
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.
PhishDestroy threat report
intark.shop is a phishing site that borrows the Kraken brand to win the trust of crypto users. PhishDestroy first flagged it on 2026-09-25, and it was still online when last checked on 2026-10-19. Its page title presents it as "KrakenSNOS AI — единый интерфейс ко всем моделям", a Russian-language pitch for a single interface to all AI models. That AI-service branding sits alongside our classification of the domain as a Kraken impersonation.
Brand-impersonation pages of this kind use a familiar exchange name to make a sign-up or login form look legitimate. Visitors are pushed to enter account credentials, one-time 2FA codes or payment details, which go straight to the operators. With a Kraken login and a fresh code, an attacker can take over the real account and withdraw funds before the owner notices. The "KrakenSNOS AI" label adds a novelty hook, a supposed all-in-one AI service, that can make the request for an account or payment seem routine.
On 2026-10-01, 7 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue, SOCRadar and VIPRE. That is a minority of engines, but seven unrelated vendors reaching the same verdict on a weeks-old domain is a meaningful signal. The domain also appears in 4 AlienVault OTX threat pulses, so other researchers are tracking it too. Beyond PhishDestroy's own listing, no other blocklist carries it yet, and many browsers may still load it without a warning.
The domain was registered through Registrar.eu on 2026-09-18, only seven days before PhishDestroy detected it. That short gap is typical of throwaway phishing domains that go live soon after purchase. The site is hosted in Finland on the VPSPay ASN network at 31.76.245.224. It uses a free, automatically issued Let's Encrypt certificate, so the padlock in the address bar only means the connection is encrypted. It says nothing about who runs the site.
If you entered Kraken credentials here, change your password at once from Kraken's official app or site. Then reset 2FA, sign out all active sessions, delete any API keys you did not create and review your withdrawal address list. If you entered card or bank details or paid for the advertised AI service, contact your card issuer to dispute the charge and block the card. Defenders should block intark.shop and its hosting IP at DNS and proxy level and search mail and web logs for earlier visits. Reports to Kraken's security team and to the hosting provider help speed takedown.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0d88a-661d-74a6-976b-e617007a46c4 |
|---|---|
| Final url | https://intark.shop/ |
| Status | 200 |
| Ip | 31.76.245.224 |
| Ptr | 31-76-245-224.rdns.vpspay.net |
| Contacted IP addresses | [
"31.76.245.224"
] |
| Asns | [
"201988"
] |
| Countries | [
"FI"
] |
| Document hash | 83724ad232c8d0607a1174d819476a0a32855f27f36aac6d25d0738008070e58 |
| Script hashes | [
"f0bbc17ae5da9beb95cacbfd74a9dedc6dac046f9edb247a60ef45b77c49ce68"
] |
| Globals | [
"requestResize"
] |
| Tls | {
"san": [
"intark.shop"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "intark.shop",
"protocol": "TLS 1.3",
"valid_to": "2026-12-17T16:59:50Z",
"valid_from": "2026-09-18T16:59:51Z"
} |
| Domain age days | 6 |
| Apex age days | 6 |
| Tls age days | 6 |
| Tls valid days | 89 |
| Requests | 4 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "KrakenSNOS",
"content-type": "text/html; charset=utf-8",
"strict-transport-security": "max-age=31536000; includeSubDomains",
"content-security-policy": "default-src 'self'; img-src 'self' data:; style-src 'self'; script-src 'self'; object-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; upgrade-insecure-requests",
"x-frame-options": "DENY\nDENY",
"x-content-type-options": "nosniff\nnosniff",
"referrer-policy": "no-referrer\nno-referrer",
"permissions-policy": "camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()",
"cross-origin-opener-policy": "same-origin",
"cross-origin-resource-policy": "same-origin"
} |
Observed: · Retrieved:
| Uuid | d9e56609-f408-4cd7-8bd0-df630ddec66f |
|---|---|
| Final url | https://intark.shop/ |
| History | [
{
"url": "https://intark.shop/",
"status": 0
}
] |
| DOM structure hash | 433a5e367a2aeb4769756ee4cc70d4ffb3e81ed2c2fddf9de5834d9d14dd2a4d |
| Domain risks | [
"New Domains",
"Security Risks",
"Newly Seen Domains"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "intark.shop",
"type": "A",
"value": "31.76.245.224"
}
] |
| Dnssec valid | false |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 51,
"malicious": 4,
"suspicious": 3,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"VIPRE": "malware",
"SOCRadar": "phishing",
"LevelBlue": "suspicious",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "suspicious",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Suspicious (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "phishing and other frauds"
} |
| First seen | 2026-09-18T17:43:15Z |
| DNS records | [
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3034::ac43:963a"
},
{
"ttl": 21600,
"type": "NS",
"value": "nancy.ns.cloudflare.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "noah.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3037::6815:bc3"
},
{
"ttl": 300,
"type": "A",
"value": "172.67.150.58"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "nancy.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.11.195"
}
] |
| Dns at | 2026-10-14T13:47:59Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"*.intark.shop",
"intark.shop"
],
"issuer": "Let's Encrypt / YE1",
"serial": "5524505fd4c5a14fc6f56299e4883812fea",
"sha256": "fe38d3bcf3314acb3fffc921dab122954375378db34f61d4aee73ba7cce541c1",
"subject": "intark.shop",
"valid_to": "2026-12-17T16:43:06Z",
"valid_from": "2026-09-18T16:43:07Z"
} |
No. PhishDestroy classifies intark.shop as a Kraken impersonation page (risk: critical, 88/100); it was first detected on 2026-09-25. VirusTotal: 7/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on intark.shop. 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.
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.
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.
nancy.ns.cloudflare.comnoah.ns.cloudflare.comLocation describes the IP network.
fe38d3bcf3314acb3fffc921dab122954375378db34f61d4aee73ba7cce541c1*.intark.shopintark.shopSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
api.intark.shopDomain recordThe original observation time is not recorded for these hostnames.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
0→1
3→Observation retained
2→3
1→2
0→1
Reachable
No threat flag
View source7/91 engine detections
View source4 community references
View sourcePD-20260925-C1ECD9
intark.shop
View sourcePage captured
View source114 stored lookalike domains
Showing 100 of 114
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
intark.shop
PD-20260925-C1ECD9 Recipient: abuse@registrar.eu 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 ↗
intark.shop)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.