Skip to security report
Domain security and threat intelligence
slon-kraken7at.ru favicon

slon-kraken7at.ru

In short

slon-kraken7at.ru is a Kraken impersonation page detected by PhishDestroy on 2026-09-26. Risk: critical (88/100). Registrar: DOMENUS-RU. Status: Last known active. Hosting: zeroms.net. PhishDestroy sent 1 abuse report. VirusTotal: 6/91 engines flag it. Do not enter credentials or connect a wallet.

“Slon-kraken7at.ru — разбираемся в выборе качественной обуви”

Registrar
DOMENUS-RU
Resolved IP
81.181.113.132
Registered
Sep 13, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 6/91 Automated brand label: Kraken
OTX: 4 refs Sep 27, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@lir.ro. The latest stored availability evidence still shows the domain reachable; 26 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.

Elapsed since first report
26 days
Reports sent
1
Latest case ID
PD-20260926-E01F35
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 6 / 91 · OTX 4 references 7 sources

VirusTotal

6 / 91 engine detections

Open report

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
6 / 91
OTX
4 community refs
Page captures
6

PhishDestroy threat report

Overview

slon-kraken7at.ru is an impersonation phishing page that borrows the Kraken name to attract people looking for that service. PhishDestroy first flagged it on 2026-09-27, and it was still online with live content on 2026-10-19. The page title is in Russian and reads as a guide to choosing quality footwear, while our classification is Kraken impersonation phishing.

How the scam works

Kraken lookalikes depend on the domain name. A visitor who searches for the brand or follows a shared link sees "kraken" in the address and assumes they have reached a working mirror or login page. These pages typically ask for a username, password and one-time 2FA code, then pass them to the operators, who log in to the real account and withdraw whatever is there. Some variants instead ask for a deposit or a top-up to unlock access, so the money is lost the moment it is sent.

Evidence

On 2026-10-03, six of 91 VirusTotal engines flagged the domain: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar, URLQuery and VIPRE. That is a minority, but these vendors work independently, and their verdicts match ours. The domain also appears in four AlienVault OTX threat pulses, so other researchers have tracked it as well. PhishDestroy lists it on its blocklist.

Infrastructure

The domain was registered on 2026-09-13 through DOMENUS-RU and was flagged by PhishDestroy 14 days later. A short gap between registration and detection is common for throwaway phishing domains that are set up quickly and replaced once they are blocked. The site is hosted in Romania on the zeroms.net network at 81.181.113.132. It has a free Let's Encrypt certificate, so the browser padlock only means the connection is encrypted and says nothing about whether the site is legitimate.

What to do

If you typed Kraken credentials into this page, change your password immediately from the official Kraken site or app and reset your 2FA. Then review active sessions, API keys and withdrawal-address whitelists for any changes you did not make. If you sent a deposit or "unlock" payment here, do not send more. Report the transfer to Kraken support and your local police with the transaction details. Defenders should block the domain and its IP and alert staff and users who trade crypto.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-26T23:26:15Z

Observed: · Retrieved:

Uuid
01a0e00a-50c6-71ec-8d82-d074e3c394f7
Final url
https://slon-kraken7at.ru/
Status
200
Ip
81.181.113.132
Contacted domains
[
    "mc.yandex.com",
    "mc.yandex.ru",
    "www.google-analytics.com",
    "www.googletagmanager.com"
]
Contacted IP addresses
[
    "216.239.32.178",
    "87.250.250.119",
    "74.125.192.97",
    "81.181.113.132"
]
Asns
[
    "15169",
    "13238",
    "215362"
]
Countries
[
    "US",
    "RU",
    "RO"
]
Document hash
d3a6843cd078cda2f4c16d30a18f8dc361cbfbfaa1600ccd63fd6d04a64af9a7
Globals
[
    "requestResize",
    "ym",
    "gtag",
    "dataLayer",
    "google_tag_data",
    "google_tag_manager",
    "gaGlobal",
    "Ya",
    "yaCounter112549444",
    "REDIRECT_URL",
    "REDIRECT_DELAY_MS",
    "layer",
    "redirectTimer",
    "scheduleRedirect"
]
Cookies
[
    "_ga_LSS3ETLT86",
    "_ga",
    "bh",
    "_ym_uid",
    "_ym_d",
    "_ym_isad",
    "sync_cookie_csrf",
    "yabs-sid",
    "i",
    "yandexuid",
    "yuidss",
    "ymex",
    "sync_cookie_csrf_secondary",
    "sync_cookie_ok_secondary",
    "_yasc",
    "_ym_visorc"
]
Storage keys
[
    "_ymBRC",
    "_ym_synced",
    "_ym112549444_lsid",
    "_ym112549444:0_reqNum",
    "_ym_uid",
    "_ym_retryReqs",
    "_ym_jn"
]
Tls
{
    "san": [
        "slon-kraken7at.ru"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YE2",
    "subject": "slon-kraken7at.ru",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-12T14:26:54Z",
    "valid_from": "2026-09-13T14:26:55Z"
}
Domain age days
13
Apex age days
13
Tls age days
13
Tls valid days
89
Requests
9
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000",
    "x-frame-options": "DENY",
    "x-content-type-options": "nosniff",
    "referrer-policy": "no-referrer",
    "permissions-policy": "camera=(), microphone=(), geolocation=()"
}
Cloudflare Radar · 2026-09-26T23:27:37Z

Observed: · Retrieved:

Uuid
456ae968-e5e1-407f-925f-5cb9c69a9e1c
Final url
https://slon-kraken7at.ru/
Status
200
History
[
    {
        "url": "https://slon-kraken7at.ru/",
        "status": 200
    }
]
DOM structure hash
fc9ec3ac66b1e7fc19389b4a928a54337bd480b8405230936370b4c64eb820bf
Document hash
d3a6843cd078cda2f4c16d30a18f8dc361cbfbfaa1600ccd63fd6d04a64af9a7
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "slon-kraken7at.ru",
        "type": "A",
        "value": "81.181.113.132"
    }
]
Dnssec valid
false
Ip
81.181.113.132
Registration record
{
    "registrar": "DOMENUS-RU",
    "created": "2026-09-13T15:02:31Z",
    "expires": "2027-09-13T15:02:31Z",
    "nameservers": [
        "ns1.domenus.ru",
        "ns2.domenus.ru"
    ]
}
VirusTotal · 2026-10-07T21:15:03Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 3,
    "suspicious": 2,
    "undetected": 34
}
Vendor labels
{
    "VIPRE": "malware",
    "SOCRadar": "suspicious",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
}
Registrar
DOMENUS-RU
First seen
2026-09-13T15:55:31Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "81.181.113.132"
    },
    {
        "ttl": 2560,
        "type": "NS",
        "value": "ns1.domenus.ru"
    },
    {
        "ttl": 2560,
        "type": "SOA",
        "rname": "support.domenus.ru",
        "value": "ns1.domenus.ru"
    },
    {
        "ttl": 2560,
        "type": "NS",
        "value": "ns2.domenus.ru"
    }
]
Dns at
2026-10-07T21:15:34Z
Jarm
28d28d28d00028d00042d42d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "slon-kraken7at.ru"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "6263a92497a33331242c286fdcbbb59ee9a",
    "sha256": "2b28b8b9efb68d81d3d8d9f03b348eeb007dce221dbeb3ee21dcad2676ec4051",
    "subject": "slon-kraken7at.ru",
    "valid_to": "2026-12-12T14:26:54Z",
    "valid_from": "2026-09-13T14:26:55Z"
}
Registration record
{
    "registrar": "DOMENUS-RU"
}

Questions about slon-kraken7at.ru

Is slon-kraken7at.ru legit?

No. PhishDestroy classifies slon-kraken7at.ru as a Kraken impersonation page (risk: critical, 88/100); it was first detected on 2026-09-26. VirusTotal: 6/91 engines flag it. Treat the site as unsafe.

Is slon-kraken7at.ru safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on slon-kraken7at.ru. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used slon-kraken7at.ru?

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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 6 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 1 report Port Scan checked Sep 27, 2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar DOMENUS-RU (Unknown)
Abuse contactabuse@lir.ro
RegistrationCreated Sep 13, 2026 (40d · New) — Expires Sep 13, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 27, 2026
DOM Analysisanalyzed Oct 9, 2026score 88/1001 brand signal
Submitted URLhttps://slon-kraken7at.ru/
Favicon Hash
Case ID
Observed page title
Slon-kraken7at.ru — разбираемся в выборе качественной обуви
Automated brand references
Kraken
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 49 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
81.181.113.132
Network ASN
AS215362
Organization
All Things IT SRL
Observed location
Bucharest, RO
Server header
nginx

Nameservers 2

  • ns1.domenus.ru
  • ns2.domenus.ru

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-13 14:26:55
Valid until
2026-12-12 14:26:54
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 07:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint2b28b8b9efb68d81d3d8d9f03b348eeb007dce221dbeb3ee21dcad2676ec4051
Certificate names · 1 SAN
  • slon-kraken7at.ru

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-23 10:43:35 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-23 10:43:35 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 10:43:35 UTC last content: 2026-10-23 10:43:35 UTC
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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
URLQuery
VIPRE

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of slon-kraken7at.ru · checked Sep 27, 2026

95
Good
Performance
FCP
0.85s
First Contentful Paint
LCP
2.43s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
84ms
Total Blocking Time
SI
4.4s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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.

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=nginx

Browser
Slon-kraken7at.ru — разбираемся в выборе качественной обуви
Crawler
Slon-kraken7at.ru — разбираемся в выборе саундбара для телевизора
slon-kraken7at.ru
Saved result
Cloaked / Filtered
Stored observation history26

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    redirected→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 21
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  16. Availability monitor · Recorded state

    live_content

    content_served

  17. VirusTotal · Detection count

    4→3

  18. VirusTotal · Detection count

    3→4

  19. VirusTotal · Detection count

    2→3

  20. VirusTotal · Detection count

    1→2

  21. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/91 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Abuse report sent

    PD-20260926-E01F35

    abuse@lir.ro
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    slon-kraken7at.ru

    View source

Lookalike domains

114 stored lookalike domains

Show all (88)
kkraken.com repetition kr2aken.com insertion kraaken.com repetition kraekn.com transposition kraen.com omission kraiken.com insertion krak3n.com replacement krake.com omission krakeb.com replacement krakeen.com repetition krakeh.com replacement krakencom.com various krakewn.com insertion krakien.com insertion krakin.com vowel-swap krakjen.com insertion krakken.com repetition krakn.com omission krakne.com transposition krakon.com vowel-swap krakren.com insertion krakrn.com replacement krakwen.com insertion krakwn.com replacement kralen.com replacement kramen.com replacement kreaken.com insertion krkaen.com transposition krken.com omission kroken.com vowel-swap krraken.com repetition krsken.com replacement kruken.com vowel-swap kryken.com replacement ktaken.com replacement lkraken.com insertion lraken.com replacement mkraken.com insertion mraken.com replacement okraken.com insertion raken.com omission rkaken.com transposition craken.com bitsquatting jraken.com bitsquatting k-raken.com hyphenation k2aken.com bitsquatting kbaken.com bitsquatting kpaken.com bitsquatting kra-ken.com hyphenation kracen.com bitsquatting krajen.com bitsquatting krak-en.com hyphenation krakan.com bitsquatting krakel.com bitsquatting kraken1.com addition kraken2.com addition kraken3.com addition kraken4.com addition kraken5.com addition kraken6.com addition kraken7.com addition kraken8.com addition kraken9.com addition krakena.com addition krakenc.com addition krakene.com addition krakenf.com addition krakeng.com addition krakenh.com addition krakeni.com addition krakenk.com addition krakenl.com addition krakenn.com addition krakeno.com addition krakenr.com addition krakens.com addition krakent.com addition krakenv.com addition krakenx.com addition krakeny.com addition krakenz.com addition kraker.com homoglyph krakgn.com bitsquatting krakmn.com bitsquatting krakun.com bitsquatting kreken.com bitsquatting kriken.com bitsquatting kvaken.com bitsquatting

Showing 100 of 114

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260926-E01F35 Recipient: abuse@lir.ro
Page title stored with report: Slon-kraken7at.ru — разбираемся в выборе качественной обуви
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

7 evidence signal groups linked 1 stored notification records Last known active
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.

Official reporting routes

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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including slon-kraken7at.ru)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/slon-kraken7at.ru"
  title="PhishDestroy threat report for slon-kraken7at.ru"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>