allocation-standardreserve.xyz is a Firelight impersonation page detected by PhishDestroy on 2026-09-29. Risk: critical (100/100). Registrar: Eranet International. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 4/91 engines flag it. Do not enter credentials or connect a wallet.
“Firelight – The Protection Layer for Digital Assets”
Security engines reporting a detection: 4. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
allocation-standardreserve.xyz is an impersonation phishing page that posed as Firelight under the title "Firelight – The Protection Layer for Digital Assets." It targeted crypto holders who would trust a security-branded service with their wallet. PhishDestroy first saw it on 2026-09-29. The site has been offline since 2026-09-30 and was still unreachable when last checked on 2026-10-19.
How the scam works
The page borrowed Firelight's name and its promise of protecting digital assets to make a fraudulent site look like a safeguard. The "allocation" wording in the domain fits the common lure of a token allocation or reward to claim. Pages like this typically ask visitors to connect a wallet, sign a transaction or enter a recovery phrase to "activate protection" or "claim" funds. Any of these steps can hand control of the wallet's assets to the operators. A victim who approves a malicious signature or reveals a seed phrase can lose everything the wallet holds.
Evidence
urlscan.io rated the page malicious and recognised Firelight branding on it. On VirusTotal, only 4 of 91 engines flagged the domain as of 2026-09-29: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and Gridinsoft. That low count reflects how quickly the site appeared and vanished, not a clean bill of health. The crypto-focused blocklists carry more weight here: MetaMask, ScamSniffer and SEAL all list it alongside PhishDestroy. It also appears in four AlienVault OTX threat pulses.
Infrastructure
The domain was registered on 2026-09-27 through Eranet International Limited and was being flagged two days later. It went dark the day after that, a short lifespan typical of disposable phishing domains. The site sat behind Cloudflare, Inc. on an address geolocated to Canada, so the real origin server is not visible from the outside.
What to do
If you connected a wallet to this site, use a token-approval checker to revoke any permissions you granted, and move your remaining assets to a fresh wallet. If you typed in a seed phrase or private key, treat that wallet as compromised and transfer the funds immediately, because revoking approvals will not protect it. Reach Firelight only through its official channels, not through links promising allocations. Defenders should block the domain and check logs for visits around 2026-09-29 to 2026-09-30. Watch for lookalike names that pair allocation or reserve wording with security brands.
No. PhishDestroy classifies allocation-standardreserve.xyz as a Firelight impersonation page (risk: critical, 100/100); it was first detected on 2026-09-29. VirusTotal: 4/91 engines flag it. Treat the site as unsafe.
Is allocation-standardreserve.xyz safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on allocation-standardreserve.xyz. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used allocation-standardreserve.xyz?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
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 29, 2026
DOM Analysisanalyzed Sep 29, 2026score 100/1001 brand signal
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.
Accreditation is a contract, not a safety certification.
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.222.132
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
devin.ns.cloudflare.com
pola.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
YE1
Valid from
2026-09-27 18:08:47
Valid until
2026-12-26 18:08:46
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint62dc3a8b157c8f7f490706eac5442b22efb5857104775d286c0c3bd605e0f883Certificate names · 2 SANs
*.allocation-standardreserve.xyz
allocation-standardreserve.xyz
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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 matches6
Same favicon hash or the same page title as this host.
6 evidence signal groups linked1 stored notification recordsContent unavailable
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 allocation-standardreserve.xyz)
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.
(US)
