跳转到安全报告
域安全和威胁情报
event-community.net favicon

event-community.net

“Brad Garlinghouse 100,000,000 #XRP Reward Program”

注册商
Global Domain Group
Resolved IP
188.114.96.3
Registered
2026年10月12日
PhishDestroy assessment 关键
可用性 可达 · 访问受限 可达响应;页面内容未经验证 观察到 · HTTP probe
病毒检测总数:1/92 自动品牌标签:Ripple 年轻域名:8 天龄 最后已知的活跃状态 Google Safe Browsing: threat flag recorded
OTX: 3 refs 2026年10月15日 1 Report Sent CDN
API
该域名已被标记为恶意域名
安全引擎报告检测:1。 请格外小心——不要输入凭据或个人信息。
ABUSE NOTICE · 72H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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.

Elapsed since first report
4 days
Reports sent
1
Latest case ID
PD-20261015-B07817
Current status
HTTP 403 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
报告概览

冒充 Ripple: event-community.net — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 1/92 (SOCRadar); URLQuery 2 det.; URLScan malicious verdict; Google Safe Browsing…

为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。

Source evidenceVirusTotal 1 / 92 · Google Safe Browsing: flagged · OTX 3 references 6 sources

VirusTotal

1 / 92 engine detections

打开报告

Google Safe Browsing

Threat flag recorded

打开报告

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

关键
VirusTotal
1 / 92
OTX
3 community refs
Page captures
3

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

已保存的截图 · 3 captures

Domain details

域名
URLScan verdict 恶意 score 100 Phishing brand: Ripple report ↗
Google Safe Browsing 已标记 Social engineering checked 2026年10月17日
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX tags 2026-10all-domainsblocklistcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 Global Domain Group US(US)
滥用举报联系方式abuse@globaldomaingroup.com
ICANN 注册管理机构ICANN Lookup (RDAP) →
注册信息创建 2026年10月12日 (8d · Very New!) — Expires 2027年10月12日
HTTP 状态码403 Forbidden
Elapsed Since First Report 29h
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 可达 · 访问受限.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年10月15日
DOM Analysisanalyzed 2026年10月15日score 100/100
Submitted URLhttps://event-community.net/xrp/
Favicon Hash
案件 ID
Observed page title
Brad Garlinghouse 100,000,000 #XRP Reward Program
TLS 证书
颁发者 Let's Encrypt / YE1 · stored validity ends in 81 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP 声誉不属于此域。

域名服务器 2

  • norman.ns.cloudflare.com
  • susan.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / YE1
Valid from
2026-10-12 13:22:32
Valid until
2027-01-10 13:22:31
Validity
Within stored validity dates
Collection time
2026-10-15 19:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta070ef66502cefb93ba04ef9dbacacdf953dce319b0977bfdc919da69e32efec

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Recorded subdomains1

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 record

The original observation time is not recorded for these hostnames.

技术 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

1 / 92 安全供应商标记了该域
View on VT
Last analyzed First positive detection
SOCRadar

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
网站性能分析

Google PageSpeed Insights — mobile performance audit of event-community.net · checked Oct 15, 2026

79
Needs Work
Performance
FCP
1.93s
First Contentful Paint
LCP
3.69s
Largest Contentful Paint
CLS
0.151
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.7s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://event-community.net/xrp/
Ripple — Participate
响应
HTTP 200
HTML body
26.4 KB
Compressed
6.5 KB
Links
1 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 2e0783875bacb160ffecad5efa5bac774aed13e62f2e4afdd1c583e17aa96af5
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4b08ec0b9349180-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Thu, 15 Oct 2026 17:31:29 GMT
Last-Modified
Mon, 12 Oct 2026 10:30:39 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=SeyTIe4CN6heTXYvEPM%2F969t%2BL%2BJ9Iz9s8o%2Ba4ZHYuTyHvkAO12v2tohvKttD2T41Akz%2Fz5Ox3Uf4DArYDWScuVzrfql%2F5wWkFvLYXNeNrsl3tHpQxGABoVkMH8C%2FZCjQ
Server
cloudflare
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Registration & observation details2

Availability observations

Last reachable observation
Last content observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial

Browser
Brad Garlinghouse 100,000,000 #XRP Reward Program
Crawler
Suspected Phishing | Cloudflare
event-community.net
Stored observation history8

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    未知→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    可访问→不可用

  5. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

Earlier observations 3
  1. Availability monitor · Recorded state

    未知→live_content

    content_served

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  3. Availability monitor · First collection record

    可访问

Recorded activity

6 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. AlienVault OTX

    3 community references

    View source
  3. VirusTotal

    1/92 engine detections

    View source
  4. Abuse report sent

    PD-20261015-B07817

    abuse@globaldomaingroup.com
  5. Added to PhishDestroy

    event-community.net

    View source
  6. URLScan

    Page captured

    View source

证据与外部报告

已提交证据快照
Sent: Ledger records: 1 Case ID: PD-20261015-B07817 Recipient: abuse@globaldomaingroup.com
Page title stored with report: Ripple — Participate
PDF notice generated
深度分析
Help & reporting

您是否受到本网站的影响?

6 evidence signal groups linked 1 stored notification records 可达 · 访问受限
If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。

Official reporting routes

警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident

针对受害者的建议与指导

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.

  • 更改所有密码 — 电子邮件、Exchange 账户,以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用(而非短信)。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息?

联邦调查局(FBI)指南

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.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 event-community.net)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。

我应该向哪里举报这起诈骗?

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动,也能留下正式记录

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?

  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前,请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

随时掌握最新信息,确保安全

请实时监控威胁,或者如果您认为这是误报,请对该条目提出异议

实时威胁动态 对该列表提出异议
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/event-community.net"
  title="PhishDestroy threat report for event-community.net"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>