VirusTotal
17 / 89 engine detections
Відкрити звіт“soumken | AI Trading Platform | Official Website”
фішинг: soumken.com — Контент недоступний. Зведення доказів: VirusTotal 17/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 5…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
17 / 89 engine detections
Відкрити звіт5 threat-system alerts
Відкрити звітШкідливий
Відкрити звіт5 community references
Відкрити звітNo threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Quad9 DNS | soumken.com |
malicious | Sinkholed |
| Cloudflare DNS | soumken.com |
malicious | Sinkholed |
| DigiCert UltraDNS | soumken.com |
malicious | Sinkholed |
| OpenDNS | soumken.com |
phishing | Phishing Block |
| DNS4EU | soumken.com |
malicious | Sinkholed |
PhishDestroy threat report
soumken.com is a fraudulent crypto trading site that presented itself as "soumken | AI Trading Platform | Official Website". It targets people looking for automated, AI-driven crypto returns and tries to get them to deposit money. PhishDestroy first detected it on 2026-09-16 and classifies it as a fake exchange. The site has been offline since 2026-09-22, and its DNS was still inactive when checked on 2026-10-19.
Fake AI trading platforms promise that an algorithm will grow your crypto with little effort. Victims open an account and send funds to a deposit address controlled by the operators. A dashboard then shows invented profits to encourage larger deposits. Withdrawals are blocked or tied to new "fees" or "taxes", and the deposited money is never returned. When such a site disappears, as this one did, all balances shown to users vanish with it.
On 2026-09-18, VirusTotal showed 17 of 89 security engines flagging the domain. The flagging vendors include alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker and Fortinet. The domain appears in 5 AlienVault OTX threat pulses and is listed on the PhishDestroy blocklist.
The domain was registered on 2026-06-16 through MainReg Inc., about three months before it was detected. It was hosted at 185.62.57.48 on the Snel.com B.V. network in the Netherlands. Its TLS certificate was issued by ZeroSSL ECC DV SSL CA 2. A certificate like this only encrypts the connection and says nothing about whether the site is trustworthy.
If you registered on soumken.com, change the password anywhere you reused it and turn on two-factor authentication. If you sent funds, gather your transaction IDs, deposit addresses and any chats with "support" or "account managers". Report the loss to your bank or the exchange you sent from, and to local police or a cybercrime unit. Ignore anyone who offers to recover the money for a fee, because recovery scams commonly target victims of fake exchanges. Defenders should block the domain and IP 185.62.57.48 and watch for look-alike AI trading brands using the same pattern.
eoin.ns.cloudflare.comzainab.ns.cloudflare.comLocation describes the IP network.
122cd339bb873df90aa51df5d35453ad352e87fe2ddc4a7c2a69834219b118a7Saved 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 soumken.com · checked Sep 16, 2026
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.
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Доступний→Недоступно
Доступний
No threat flag
View source5 community references
View source17/89 engine detections
View sourcePD-20260916-1CD24E
Page captured
View sourcesoumken.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
soumken.com
PD-20260916-1CD24E Recipient: complain@mainreg.com Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
soumken.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.