VirusTotal
7 / 89 engine detections
打开报告“Arc Creator Settlement — Verifiable USDC milestone payments”
冒充 MetaMask: creatorsettle.com — 最后已知的活跃状态 (HTTP 308). 证据摘要: VirusTotal 7/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
7 / 89 engine detections
打开报告DBL_PHISH
4 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
creatorsettle.com poses as an "Arc Creator Settlement" platform, presenting itself as a legitimate USDC milestone payment portal aimed at content creators who might believe they are owed funds. PhishDestroy first identified it on 2026-09-11, one day after the domain was registered on 2026-09-10. The site remains alive and reachable as of 2026-10-18, meaning it is still actively capable of harming visitors.
The site uses the page title "Arc Creator Settlement — Verifiable USDC milestone payments" to convince targets they have a legitimate USDC payout waiting for them. Victims are prompted to connect their cryptocurrency wallet to claim the supposed settlement funds. Once a wallet is connected, the drainer silently requests broad token approvals or executes malicious transactions that transfer the victim's assets to the attacker, emptying the wallet without any settlement ever being paid.
Seven of 89 engines on VirusTotal flagged this domain as malicious as of 2026-09-21, with detections from alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar, and VIPRE. Spamhaus DBL lists it under the DBL_PHISH category, independently confirming its phishing nature. Four OTX pulses have also been published against this domain, and PhishDestroy carries it on its own blocklist. Detection coverage is moderate rather than universal, which underscores why the site remains reachable.
The domain was registered on 2026-09-10 through Cloudflare, Inc. and is hosted on Amazon.com, Inc. infrastructure in the United States at IP 76.76.21.21. TLS is provided by Let's Encrypt under the YR1 issuer, giving the site a padlock that conveys no trustworthiness. The combination of same-day registration and immediate deployment is consistent with a purpose-built fraud operation.
If you visited the site but did not connect a wallet or enter any credentials, no immediate action is required beyond avoiding the site entirely. If you connected a wallet, immediately use a trusted revocation tool to cancel all token approvals granted to any contract associated with this site, and transfer remaining assets to a fresh wallet address. If you entered personal information, monitor those accounts closely and consider changing associated passwords. Security teams and platform defenders should block creatorsettle.com at the DNS and network perimeter levels and alert any creator communities that may have been targeted by this campaign.
Edge-IP 声誉不属于此域。
emma.ns.cloudflare.comjay.ns.cloudflare.comLocation describes the IP network.
156fd8bde15f7bb9b9fdb01241e951add7ba77ece227b7a2f91fd8d15b5f8dcfwww.creatorsettle.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of creatorsettle.com · checked Sep 11, 2026
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.
creatorsettle.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
protected→redirected
http_redirect
未知→protected
http_access_restricted · access_restriction
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
可访问
4 community references
View sourceNo threat flag
View source7/89 engine detections
View sourcecreatorsettle.com
View sourcePage captured
View source已存储 79 个仿冒域名
Listed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
creatorsettle.com)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.