PhishDestroy’s intake system classified rabbyweb.cloud as malicious following an admin report and an AI‑driven phishing confidence of 95 %. The prior AI assessment observed that the site uses the Rabby Wallet brand in its title and offers actions such as “Create a new address” or “I already have an address”, which match typical wallet‑impersonation patterns. The domain was first seen by PhishDestroy on 2026-10-21 and returned an HTTP 200 response at that time.
How the scam works
Impersonation wallets present a replica of a legitimate wallet interface and solicit users to enter seed phrases, private keys, or to approve transactions, enabling attackers to gain control of funds. By mimicking the Rabby Wallet brand and prompting address creation, such pages aim to trick users into disclosing credentials or authorizing transfers.
Evidence
VirusTotal scanned the domain on 2026-10-21 with 92 engines and reported zero malicious or suspicious detections. Google Safe Browsing checked the same day and did not flag the URL. OTX listed three pulses referencing the domain on 2026-10-21, but none constitute a confirmed malicious event. URLScan’s machine‑learning engine marked the page malicious with a score of 99, while its overall verdict was non‑malicious. PhishDestroy’s internal blocklist also contains rabbyweb.cloud.
Infrastructure
The domain was registered with Dynadot on 2026-10-16. At the time of observation the DNS records returned two A addresses, 63.176.8.218 and 35.157.26.135, both belonging to Amazon Technologies. The TLS certificate, issued by Let’s Encrypt, covered *.rabbyweb.cloud and was valid until 2027-01-14; the server header captured in the response identified Netlify, and DNSSEC was not present.
What to do
Users should avoid entering any wallet credentials on this site and consider creating a new wallet if they suspect compromise. Defenders should block rabbyweb.cloud at the network perimeter, monitor for traffic to the recorded IP addresses, and update threat‑intel feeds with this indicator.
RegistrationCreated Oct 16, 2026 (5d · Brand New!)—Expires Oct 16, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 21, 2026
DOM Analysisanalyzed Oct 21, 2026score 83/1002 brand signals
Submitted URLhttp://rabbyweb.cloud/
Favicon Hash
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
63.176.8.218
Network ASN
AS16509
Organization
Amazon Technologies Inc.
Observed location
Frankfurt, DE
Server header
Netlify
Edge-IP reputation is not attributed to this domain.
Nameservers 4
dns1.p08.nsone.net
dns2.p08.nsone.net
dns3.p08.nsone.net
dns4.p08.nsone.net
Location describes the IP network.
TLS certificate
Issuer
YE1
Valid from
2026-10-16 16:45:06
Valid until
2027-01-14 16:45:05
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintd31c625f6886ab1a8cb4d7c433ac8806066f72a3211167ec971dff5c8536a08fCertificate names · 2 SANs
*.rabbyweb.cloud
rabbyweb.cloud
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-21 23:03:56 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-21 23:03:56 UTClast content: 2026-10-21 23:03:56 UTC
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.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · rabbyweb.cloud
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.
3 evidence signal groups linked0 stored notification recordsLast known active
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 rabbyweb.cloud)
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)
