VirusTotal
1 / 93 engine detections
فتح التقرير“YieldScan Terminal | Ecosystem Intelligence”
احتيال الاستثمار في العملات المشفرة: yieldscan.finance — المحتوى غير متوفر. ملخص الأدلة: VirusTotal 1/93 (SOCRadar); URLQuery 1 alert; PhishDestroy score…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
1 / 93 engine detections
فتح التقرير1 threat-system alert
فتح التقريرSuspicious
فتح التقرير3/14
no community references
فتح التقريرNo threat flag
فتح التقريرPage capture
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| YARAhub by abuse.ch | yieldscan.finance/ |
malware | Detects file containing Telegram Bot API |
PhishDestroy threat report
Analysis as of July 24, 2026 indicates that the domain yieldscan.finance was registered on February 23, 2026 through Hostinger operations, UAB and is currently taken offline. The domain resolves to the IPv4 address 92.113.23.14, which belongs to AS47583 Hostinger International Limited located in Germany. DNS resolution is handled by ns1.dns-parking.com and ns2.dns-parking.com, both typical of parking services. No SSL certificate was observed, meaning the site does not provide encrypted HTTPS connections. The page title returned from the host is "YieldScan Terminal | Ecosystem Intelligence," suggesting an attempt to present a legitimate financial‑technology interface.
Detected technologies include Hostinger CDN, Google Analytics, and HTTP/3, indicating use of common web‑hosting and analytics stacks but no specialized malicious kit. The domain is classified as an investment scam and appears on three independent security blocklists, with active blocking enforced by PhishDestroy, MetaMask, and SEAL. Reputation scoring from Gridinsoft assigns a score of 0 out of 100, reflecting extreme distrust. VirusTotal analysis shows that one of ninety‑three scanning engines flagged the domain, confirming at least one detection of malicious behavior.
The low trust score, absence of TLS, blocklist inclusion, and the single vendor flag collectively point to a high‑confidence malicious profile despite the limited number of detections. Uncertainty remains around the exact payload or credential‑harvesting mechanisms because no page content was captured; the analysis is limited to infrastructure and metadata. Defenders should continue to block the domain at network perimeters, monitor DNS queries for the associated IP and nameservers, and ensure that any client‑side applications that might contact the site are patched or restricted. Ongoing surveillance of the IP address and related Hostinger assets is advised, as the infrastructure could be repurposed for future campaigns.
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.
ns2.dns-parking.comLocation describes the IP network.
Saved 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 yieldscan.finance · checked Mar 6, 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
يمكن الوصول إليه→غير متوفر
1→2
https://radar.cloudflare.com/scan/cbcd3c43-e508-4d6c-add2-c346bdf90e9f
No threat flag
View source1/93 engine detections
View sourceyieldscan.finance
View sourcePD-20260223-AC1FD7
Page captured
View sourceأبلغ عنه عضو واحد في المجتمع؛ شوهد أول مرة في 23/02/2026
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
yieldscan.finance
PD-20260223-AC1FD7 Recipient: report@abuseradar.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 ↗
yieldscan.finance)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.