allocation-standardreserve.icu 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: 8/91 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.
“Firelight – The Protection Layer for Digital Assets”
Security engines reporting a detection: 8. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
allocation-standardreserve.icu is an impersonation phishing page posing as Firelight under the title "Firelight – The Protection Layer for Digital Assets". The domain pairs "allocation" with "standard reserve", wording that fits a fake token-allocation or reward claim aimed at people who hold or follow Firelight. PhishDestroy first saw it on 2026-09-29. It went offline on 2026-09-30, and as of 2026-10-19 its DNS no longer resolves.
How the scam works
The page borrows Firelight's name and tagline so visitors believe they are on the real project's site, likely to claim an allocation. Pages like this usually ask the visitor to connect a wallet and approve or sign transactions presented as a claim or verification step. Those signatures can hand control of tokens to the attacker, or the page may ask for a seed phrase outright. Either way the victim can lose the assets in the connected wallet.
Evidence
Eight of 91 VirusTotal engines flagged the domain on 2026-09-29: alphaMountain.ai, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Kaspersky and Netcraft. That count is modest, but these vendors agreed within a day of the site appearing. Google Safe Browsing lists it as social engineering, and urlscan.io returned a malicious verdict and identified Firelight branding on the page. The wallet-focused blocklists of MetaMask, ScamSniffer and SEAL include it alongside PhishDestroy, and three AlienVault OTX pulses reference it.
Infrastructure
The domain was registered on 2026-09-27 through Eranet International Limited, two days before PhishDestroy detected it. It was offline about three days after registration, which matches a throwaway domain built for a short burst of traffic. The site sat behind Cloudflare, Inc. on an address placed in Canada, so the real origin server was not exposed. The cheap .icu extension and the generic, finance-flavoured name fit a disposable lure rather than anything tied to the real Firelight project.
What to do
If you connected a wallet to this site, use a token-approval checker to revoke any permissions you granted while it was live. Move remaining funds to a fresh wallet if you signed anything you did not fully understand. If you typed in a seed phrase, treat that wallet as compromised and transfer everything to a new wallet created with a new phrase immediately. Reach Firelight only through its official channels and ignore allocation claims promoted in direct messages or replies. Security teams should block the domain and watch for lookalike .icu domains using allocation or reserve wording with Firelight branding.
No. PhishDestroy classifies allocation-standardreserve.icu as a Firelight impersonation page (risk: critical, 100/100); it was first detected on 2026-09-29. VirusTotal: 8/91 engines flag it. Google Safe Browsing flags it. Treat the site as unsafe.
Is allocation-standardreserve.icu safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on allocation-standardreserve.icu. 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.icu?
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
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.157.138
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
aaden.ns.cloudflare.com
nia.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
YE1
Valid from
2026-09-27 17:39:23
Valid until
2026-12-26 17:39:22
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint350b877550c0f19441d3c7fb4b2553fac3596c19de28c56644b9e5c933bf539cCertificate names · 2 SANs
*.allocation-standardreserve.icu
allocation-standardreserve.icu
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-21 01:17:11 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-29 10:06:03 UTCcurrent episode first observed: 2026-10-01 16:16:25 UTCobserved RIP window: 2026-09-29 10:06:03 UTC → 2026-10-01 16:16:25 UTC · 54.17hmidpoint estimate ≈ 2026-09-30 13:11:14 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 · 5 identified
F
Framer Sites
CMSPage builders
Framer is a no-code web design platform for designing and publishing responsive websites.
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.icu)
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)
