VirusTotal
15 / 92 engine detections
فتح التقريرتصيد: steomes.com — آخر نشاط معروف (HTTP 301). ملخص الأدلة: VirusTotal 15/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker)…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
15 / 92 engine detections
فتح التقريرSuspicious
فتح التقرير2 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.
PhishDestroy threat report
steomes.com is on the PhishDestroy blocklist as a suspicious domain. It does not serve a page of its own. It sends visitors on to another destination. PhishDestroy first saw it on 2026-10-06. As of 2026-10-19 it was still online and still redirecting, so anyone clicking a link to it today is passed along to whatever it currently points at.
No impersonated brand or specific scheme has been confirmed for this domain. A redirecting domain is often used as a disposable front: links to it go out in messages, posts or ads, and the real landing page can be swapped at any time without changing the link. In the crypto space, that landing page is often a fake login, a wallet-connect prompt or a deposit form. Treat any page you reach through steomes.com as untrusted, and never enter credentials, seed phrases or wallet signatures there.
On 2026-10-10, 15 of 92 VirusTotal engines flagged the domain. They included alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. That many independent vendors agreeing on one domain is a strong signal, well beyond a single false positive. The domain also appears in two AlienVault OTX threat pulses, so other researchers have tied it to malicious activity.
The domain was registered on 2026-05-20 through Global Domain Group LLC, about four and a half months before PhishDestroy picked it up. A domain held quietly for months and then used later is a common pattern for throwaway redirect infrastructure. It resolves to 66.198.225.39, located in the US, on a network registered to SKN Subnet & Telecom Ltd of Saint Kitts and Nevis. Its certificate is a free, automatically issued Let's Encrypt one, so the padlock in the browser says nothing about whether the site is legitimate.
If you opened a link to steomes.com, close the page you landed on and do not act on anything it asked for. If you typed a password there, change it wherever you use it and turn on app-based 2FA. If you connected a crypto wallet or signed anything, revoke the approvals from that session in a token-approval manager, and move funds to a fresh wallet if you shared a seed phrase. Security teams should block the domain and its IP at DNS and proxy level and search their logs for earlier visits.
ns3.nameserverhub.comLocation describes the IP network.
5bfc95832a5609423b8c967c5801128b10f9ab814dcfd734b6053b9bf55afb6fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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
غير معروف→redirected
http_redirect
No threat flag
View source15/92 engine detections
View source2 community references
View sourcesteomes.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
steomes.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 ↗
steomes.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.