URLScan
ضار
فتح التقرير“Suspected Phishing | Cloudflare”
انتحال Cloudflare: ldgr-submit.sdhsged.workers.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 0/89; URLScan malicious verdict…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
ضار
فتح التقرير0 / 89 engine detections
فتح التقريرno community references
فتح التقريرprovider verdict: clean
فتح التقريرNo threat flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ldgr-submit.sdhsged.workers.dev is an impersonation phishing page hosted on a Cloudflare Workers subdomain. The "ldgr-submit" label and urlscan.io's Ledger brand detection show it was aimed at owners of Ledger hardware wallets. PhishDestroy first flagged it on 2026-09-10. It went offline on 2026-09-11, and when last checked on 2026-10-19 the site was dead with its content blocked by the provider.
Pages built around a "submit" step for Ledger users usually claim the wallet needs verification, syncing or recovery. They then ask the visitor to type in the 24-word recovery phrase. Anyone who enters that phrase gives the operator full control of every account it secures, and funds can be swept without the physical device. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial, while we classified the site as an impersonation of Cloudflare.
On 2026-09-10, VirusTotal showed 0 detections out of 89 engines, so traditional antivirus vendors had not caught it when it surfaced. urlscan.io independently rated the page malicious and identified Ledger branding on it. PhishDestroy is the only blocklist carrying the domain, and the hosting provider's own block of the content supports the verdict.
The site ran on Cloudflare's free Workers platform, under a throwaway account name ("sdhsged") on the shared workers.dev domain registered through Cloudflare, Inc. It resolved to 104.21.3.246 on CLOUDFLARENET in the US. Because no domain purchase is needed, a page like this can be stood up in minutes and abandoned just as quickly. This one lasted roughly a day between our first sighting and going offline.
If you typed your Ledger recovery phrase into this page, treat that wallet as compromised. Reset your device, generate a new phrase and move any remaining funds to the new accounts right away. Ledger never asks for your recovery phrase on a website. If you connected a wallet, review and revoke any token approvals you do not recognise. Defenders should block this hostname, watch for workers.dev subdomains combining wallet-brand fragments with words like "submit", and report new instances to Cloudflare's abuse team.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
sdhsged.workers.dev*.sdhsged.workers.devSaved 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 ldgr-submit.sdhsged.workers.dev · checked Sep 10, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ldgr-submit.sdhsged.workers.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
يمكن الوصول إليه→غير متوفر
يمكن الوصول إليه
No threat flag
View source0/89 engine detections
View sourceldgr-submit.sdhsged.workers.dev
View sourcePage captured
View source١٤٢ نطاقًا متشابهًا محفوظًا
عرض 100 من 142
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 ↗
ldgr-submit.sdhsged.workers.dev)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.