VirusTotal
1 / 92 engine detections
Buka laporan“Brad Garlinghouse 100,000,000 #XRP Reward Program”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@globaldomaingroup.com.
The latest stored availability evidence still shows the domain reachable; 4 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Peniruan Ripple: event-community.net — Dapat dijangkau · akses dibatasi (HTTP 403). Ringkasan bukti: VirusTotal 1/92 (SOCRadar); URLQuery 2 det.; URLScan…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
1 / 92 engine detections
Buka laporan2 det.
Buka laporanSuspicious
Buka laporanThreat flag recorded
Buka laporanBerbahaya
Buka laporan3 community references
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
event-community.net is an impersonation phishing page built around Ripple. It used the title "Brad Garlinghouse 100,000,000 #XRP Reward Program" to pose as an official giveaway from Ripple's CEO and to lure XRP holders. PhishDestroy first flagged it on 2026-10-15. The site has been offline since 2026-10-17, with its content blocked by the provider, and it was still down at the last check on 2026-10-19.
Fake CEO giveaways like this borrow a famous name and an enormous prize pool to make a too-good-to-be-true offer feel official. The usual demand is a "verification" or "participation" transfer of XRP, with a promise that the sender will receive a multiplied amount back. Some versions instead ask visitors to enter a wallet secret phrase to "claim" the reward. No reward ever arrives. Any XRP sent is gone for good, and a disclosed secret phrase gives the scammers full control of the wallet.
Google Safe Browsing labels the domain as social engineering. urlscan.io returned a malicious verdict and recognised Ripple branding on the page. On VirusTotal, only 1 of 92 engines (SOCRadar) flagged it as of 2026-10-15. That low count reflects how new the domain was, and it does not mean the site is safe. The domain also appears in 3 AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2026-10-12 through Global Domain Group LLC and was already serving the fake reward page when PhishDestroy saw it three days later. That short gap fits a throwaway domain set up for a single campaign. Traffic went through Cloudflare (AS13335) in the US, which hides the operator's origin server from visitors.
If you sent XRP to this "reward program", treat the funds as lost and do not send more to "unlock" a payout. Report the transaction to the exchange or wallet provider you used, and be wary of anyone who later offers to recover the money for a fee. If you typed your secret phrase into the site, create a new wallet on a trusted device right away and move any remaining assets there. Remember that Ripple and its executives do not run giveaways that require you to send funds first. Defenders should block event-community.net and watch for new domains that reuse Garlinghouse or XRP reward wording.
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
norman.ns.cloudflare.comsusan.ns.cloudflare.comLocation describes the IP network.
a070ef66502cefb93ba04ef9dbacacdf953dce319b0977bfdc919da69e32efecSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.event-community.netDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of event-community.net · checked Oct 15, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://event-community.net/xrp/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gzip2e0783875bacb160ffecad5efa5bac774aed13e62f2e4afdd1c583e17aa96af5h3=":443"; ma=86400DYNAMICa4b08ec0b9349180-FRAkeep-alivegziptext/htmlThu, 15 Oct 2026 17:31:29 GMTMon, 12 Oct 2026 10:30:39 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=SeyTIe4CN6heTXYvEPM%2F969t%2BL%2BJ9Iz9s8o%2Ba4ZHYuTyHvkAO12v2tohvKttD2T41Akz%2Fz5Ox3Uf4DArYDWScuVzrfql%2F5wWkFvLYXNeNrsl3tHpQxGABoVkMH8C%2FZCjQcloudflarechunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
event-community.net
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Tidak diketahui→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Tidak diketahui→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Tidak diketahui→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Dapat dijangkau→Tidak tersedia
live_content→redirected
http_redirect
Tidak diketahui→live_content
content_served
No flag recorded→Flag recorded
Dapat dijangkau
Threat flag recorded
View source3 community references
View source1/92 engine detections
View sourcePD-20261015-B07817
event-community.net
View sourcePage captured
View sourcePD-20261015-B07817 Recipient: abuse@globaldomaingroup.com Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
event-community.net)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.