rewards-zama.lol is a MetaMask impersonation page detected by PhishDestroy on 2026-09-29. Risk: critical (95/100). Registrar: Eranet International. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 2/91 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 2. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
rewards-zama.lol is an impersonation phishing page that copied the identity of Zama, presenting itself under the title "Zama: The Confidential Blockchain Protocol". The "rewards" prefix targets Zama followers and crypto users hoping to claim tokens or incentives tied to the project. PhishDestroy first detected it on 2026-09-29. The site has been offline since 2026-09-30 and was still dead when checked on 2026-10-19.
How the scam works
The page reuses Zama's real branding and tagline so a visitor believes they have reached an official rewards or claim portal. Pages built this way usually ask the visitor to connect a wallet and approve or sign something to "receive" the reward. That signature or approval is what the operator wants, because it can let them move tokens out of the victim's wallet. Zama does not hand out rewards through look-alike domains like this one.
Evidence
On 2026-09-29, two of 91 VirusTotal engines flagged the domain: Forcepoint ThreatSeeker and LevelBlue. That count is low, which is typical for a domain caught within a day of going live, before most vendors had reviewed it. The wallet-focused blocklists carry more weight here. Besides PhishDestroy, the domain is listed by MetaMask and SEAL, and it appears in two AlienVault OTX threat pulses.
Infrastructure
The domain was registered through Eranet International Limited on 2026-09-28, one day before PhishDestroy flagged it. It went dark the day after that. A lifespan of about 48 hours is common for throwaway phishing domains, which are spun up quickly for a campaign and dropped once detected. Traffic was served through Cloudflare's network (188.114.97.3, geolocated to CA), so the real origin server was hidden. The site had a free Let's Encrypt certificate, so the padlock in the browser said nothing about whether it was legitimate.
What to do
If you connected a wallet to this site, use a token-approval checker to review your approvals and revoke any you don't recognize, especially ones granted on or around 2026-09-29. If you signed a message or approved a transaction there, move your remaining assets to a fresh wallet. If you entered a seed phrase, treat that wallet as fully compromised and stop using it. Only follow Zama announcements from its verified channels. Security teams should block the domain and watch for other "rewards" or "claim" look-alikes that use the Zama name.
No. PhishDestroy classifies rewards-zama.lol as a MetaMask impersonation page (risk: critical, 95/100); it was first detected on 2026-09-29. VirusTotal: 2/91 engines flag it. Treat the site as unsafe.
Is rewards-zama.lol safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on rewards-zama.lol. 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 rewards-zama.lol?
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 83/1001 brand signal
IoC Extractionscanned Sep 30, 20260 wallet · 1 Telegram IoC
Submitted URLhttp://rewards-zama.lol/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
julian.ns.cloudflare.com
raina.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-09-28 12:23:39
Valid until
2026-12-27 12:23:38
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-09-29 07:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb5c500f60a16a52ea8b0946a000e5562697400c9883ae656b66de33e88a21c7fCertificate names · 2 SANs
*.rewards-zama.lol
rewards-zama.lol
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.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · rewards-zama.lol
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 matches4
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 rewards-zama.lol)
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.
