The site claim-xrpl.org uses Xaman branding to present an XRP Ledger notice about evolving keys and asks visitors to click continue. Anyone who followed prompts on this page should immediately review wallet permissions and disconnect any linked sessions.
Page title: “Your keys, evolving. | Xaman”
More about the sources
Recorded security signals
Stored VirusTotal result: 3/92 engines flagged. Malicious: 2. Suspicious: 1. Analysis time (as stored): 2026-11-21 02:16 UTC. Retrieved (as stored): 2026-11-21 18:14 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Risk signals
VirusTotal detections: 3/92Stored blocklist matches: 2Young domain: 3 days old
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded claim-xrpl.org on 2026-11-21. Stored VirusTotal result: 3/92 engines flagged. Malicious: 2. Suspicious: 1. Analysis time (as stored): 2026-11-21 02:16 UTC. Retrieved (as stored): 2026-11-21 18:14 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (evidence score 76/100). Registrar: Key-Systems. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.
Registration timeline and independent vendor detections
Because it was registered on 19 Nov 2026, 2 days before it was first reported, the timeline sharply contrasts with the polished appearance of an established ecosystem update. Furthermore, 3 of 92 VirusTotal engines flagged it on 21 Nov 2026, and MetaMask and SEAL block it, with Kaspersky, Forcepoint ThreatSeeker and Gridinsoft among the scanners flagging the URL, proving that independent security teams recognize the page as suspicious. PhishDestroy's evidence score for it is 60/100 (high).
Where this page leads and expected next steps
Pages utilizing prominent wallet branding alongside generic continuation prompts typically lead visitors toward malicious connection requests or signature prompts designed to drain assets. When users click the primary button, subsequent scripts often request permissions to access connected accounts or sign transactions under the guise of an upgrade. Since official updates from wallet providers occur directly through verified applications rather than unverified web portals, engaging with such prompts risks unauthorized wallet access.
Recommended precautions and wallet review
Visitors who have already interacted with the page or clicked continue should immediately inspect their connected wallet sessions and revoke any unfamiliar token allowances. Legitimate wallet migrations never require users to connect their accounts through unexpected third-party links found online. Always verify announcements through official communication channels before approving any external connections.
Source evidenceVirusTotal 3 / 925 sources
SourceResultRecorded · UTCOpen
VirusTotal
3 / 92 engine detections
Analysis:
Open report VirusTotalOriginal source recordObserved: 16 fields
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Source
VirusTotal
Result state
observed
Numerator
3
Denominator
92
Vendors
Forcepoint ThreatSeeker, Gridinsoft, Kaspersky
Observed at
2026-11-21 02:16:03
Checked at
2026-11-21 19:14:10
Fetched at
2026-11-21 18:14:11
Cloudflare Radar
Suspicious
Open report Cloudflare RadarOriginal source recordObserved: 12 fields
Title: Your keys, evolving. | Xaman; Robots: noindex,nofollow; Description: We're preparing the next Xaman experience for the XRP Ledger. Check back soon.
Headers: Server: cloudflare; Content type: text/html; Strict transport security: max-age=63072000; includeSubDomains; preload; Content security policy: frame-ancestors http: https:; X content type options: nosniff
Questions about claim-xrpl.org
Is claim-xrpl.org the official Xaman site?
No, the domain was registered recently on 19 Nov 2026, whereas legitimate Xaman services operate through their verified channels. Visitors should always rely on official application links rather than unfamiliar web addresses.
What happens if I clicked Continue on claim-xrpl.org?
Clicking continue on unfamiliar links can lead to malicious connection prompts or requests for wallet approvals. If you interacted with the page, check your wallet for unauthorized token allowances and revoke them immediately.
Why are security vendors flagging this domain?
The domain triggered security alerts because 3 of 92 VirusTotal engines flagged it on 21 Nov 2026, and MetaMask and SEAL block it. Reviewing these telemetry signals helps protect users from potential wallet drainers.
URLScan · 2026-11-21 1 / 2 Used in the analysisSource file SHA-256: 2d1a6956…ae04515SHA-256 of the prepared copy given to the model: 03d028c9…aff01e7Cloudflare Radar 2 / 2
Certificate fingerprint3a72eac9a3ec7dd8917c212566399df40b49282591e23e163f0948eaafddab42Certificate names · 2 SANs
*.claim-xrpl.org
claim-xrpl.org
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: Resolved
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-22 11:59 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:59 UTClast content: 2026-11-22 11:59 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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-21 17:46 UTC.
Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
4 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+39 h 29 min
Added to PhishDestroy+15 h 25 min
Wayback Machine
Page archived
+3 min
Added to PhishDestroy
claim-xrpl.org
same minute
URLScan
Page captured
+15 h 25 min
VirusTotal
3/92 engine detections
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches4
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 claim-xrpl.org)
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
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 →
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.