This throwaway address on Cloudflare's workers.dev platform hosted an impersonation phishing page built around Cloudflare's own branding. It targets everyday visitors who are used to seeing Cloudflare security and verification screens and tend to trust them. PhishDestroy first saw it on 2026-09-11. The site went offline on 2026-09-19 and was still dead, with its content blocked by the provider, when we last checked on 2026-10-19.
How the scam works
Impersonation pages of this kind copy the look of a familiar service so that a visitor follows the prompts without suspicion. Pages that borrow Cloudflare's identity usually pose as a security or "verify you are human" check. They then push the visitor to type in credentials or to follow on-screen instructions that end up handing over account access or running something harmful on their own device. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial rather than the original lure. We classified the site as impersonation phishing.
Evidence
On 2026-09-20, 11 of 89 VirusTotal engines flagged the address. They include BitDefender, ESET, Emsisoft, Fortinet, G-Data, Kaspersky, LevelBlue and Lionic, a spread of independent vendors that does not rely on any single feed. urlscan.io returned a malicious verdict and matched the page to generic Cloudflare branding, which confirms what was being imitated. The site is listed on the PhishDestroy blocklist.
Infrastructure
The operator did not register a domain. They spun up a free Cloudflare Workers subdomain under a random-looking account name. That makes the page cheap to deploy and easy to replace once it is blocked. Traffic resolved to Cloudflare's network with a Canadian location, and the certificate came from Google Trust Services, as is standard for workers.dev hosts, so the padlock said nothing about legitimacy. The page lasted about eight days from our first sighting before going dark on 2026-09-19.
What to do
If you entered a password on this page, change it at once on that service and on any other account that shares it, then turn on or reset two-factor authentication. If the page told you to copy, paste or run anything on your computer, disconnect from the network, run a full scan with a reputable security tool and check for unfamiliar programs or browser extensions. Real Cloudflare checks never ask for account passwords or ask you to run commands. Defenders should block this hostname, watch for similar random workers.dev subdomains that use Cloudflare-themed lures, and report new ones to Cloudflare's abuse team.
IP ContextCloudflare shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerCloudflare Workers
HTTP Status403 Forbidden
Elapsed Since First Report7 days
What we count
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 11, 2026
Favicon Hash
Observed page title
Suspected Phishing | Cloudflare
TLS Certificate
Issued by Google Trust Services / WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.204.84
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-07-22 08:48:53
Valid until
2026-10-20 09:47:18
Hostname coverage
Certificate hostname mismatch
Validity
Validity ends today in stored record
Collection time
2026-09-18 19:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprint101f018acbba55c7d2096990a13e77445db068a476ad6aa59b8aaaae12133074Certificate names · 1 SANs
eugeniebenoits397.workers.dev
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-11 14:28:07 UTCcurrent episode first observed: 2026-10-01 01:52:48 UTCobserved RIP window: 2026-09-11 14:28:07 UTC → 2026-10-01 01:52:48 UTC · 467.41hmidpoint estimate ≈ 2026-09-21 08:10:27 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
H
HSTS
Security
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches8
Same favicon hash or the same page title as this host.
3 evidence signal groups linked0 stored notification recordsReachable · access restricted
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including leutumn-shadow-c659.eugeniebenoits397.workers.dev)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
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.
