VirusTotal
6 / 92 engine detections
Відкрити звітфішинг: stake-core.com — Останній відомий активний (HTTP 301). Зведення доказів: VirusTotal 6/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
6 / 92 engine detections
Відкрити звіт2 community references
Відкрити звітprovider verdict: clean
Відкрити звітNo threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
stake-core.com is on the PhishDestroy blocklist as a suspicious domain. Its name pairs "stake" and "core", words common in crypto branding, but no specific brand or scheme has been confirmed. PhishDestroy first saw it on 2026-10-07. As of 2026-10-19 it was still online and redirecting visitors elsewhere instead of serving its own page.
The redirect is the main concern. A crypto-themed domain that forwards traffic can pass victims to a fake login, a fraudulent investment or staking page, or a wallet-connection prompt, and the final destination can change at any time. The risk is that a visitor ends up entering credentials, approving a wallet transaction or sending funds to a page they did not choose. Until the landing content is classified, treat anything this domain leads to as hostile.
On 2026-10-11, 6 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That is a low share of engines, but it comes from several unrelated vendors, so it is more than one isolated hit. The domain also appears in two AlienVault OTX threat pulses. PhishDestroy is the only blocklist listing it so far, so many browsers and filters may not warn users yet.
The domain was registered on 2026-08-08 through Fewmoretaps OU d/b/a Trustname.com, about two months before PhishDestroy detected it. That gap fits a domain registered in advance and put to use later. It resolves to 188.114.96.1 on Cloudflare's network (AS13335, US), which hides the real origin server behind the proxy. Its certificate from Google Trust Services (WE1) only means the connection is encrypted. The padlock says nothing about whether the site is safe.
Do not follow the redirect, connect a wallet or enter any details. If you connected a wallet after landing here, review and revoke any token approvals or permissions you granted, and move remaining assets to a fresh wallet if you signed anything you did not understand. If you typed a password or seed phrase, treat it as compromised: change the password, re-secure 2FA, and never reuse a seed phrase that has been exposed. Defenders should block the domain at DNS and proxy level, watch where the redirect points, and report it to Cloudflare and the registrar.
Репутація Edge-IP не пов’язана з цим доменом.
stevie.ns.cloudflare.comLocation describes the IP network.
f9530959380d79a0ac926201b1633054ca2940a92f22af02ec6ce0f968e85d5fSaved 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.
www.stake-core.comDomain 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.
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
No threat flag
View source6/92 engine detections
View source2 community references
View sourcestake-core.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
stake-core.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
stake-core.com)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.