Analysis of claim.fix-brevis.network indicates a crypto drainer infrastructure flagged for fraudulent activity targeting cryptocurrency users. The domain, created on February 21, 2026, resolves to IP address 172.67.204.219, hosted on Cloudflare's network (AS13335) in the United States. The site was operational under the page title 'Brevis Claim Portal,' suggesting an attempt to impersonate a legitimate token or airdrop claim process associated with the Brevis project. As of July 24, 2026, the domain is offline, though its prior activity remains under scrutiny.
Infrastructure review shows the domain holds a Gridinsoft trust score of 0/100, reflecting high-risk classification. It appears on two security blocklists, including PhishDestroy and ScamSniffer, which specialize in phishing and crypto-related fraud detection. VirusTotal reports two security vendors flagging the domain, though the limited detection count does not diminish the elevated risk assessment, particularly given the domain's offline status and prior malicious context. The SSL certificate is issued by WE1, a provider commonly used across both legitimate and malicious domains, offering no definitive signal of intent.
No evidence of a phishing kit or specific brand impersonation beyond the 'Brevis Claim Portal' title is available in current intelligence. Defenders should treat this domain as part of a crypto drainer operation, particularly in retrospective log analysis or incident response involving Brevis-themed lures. Further investigation may reveal wallet addresses, transaction patterns, or associated domains linked to this campaign. Given its current offline status, monitoring for re-emergence under similar naming conventions or infrastructure is recommended.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='claim.fix-brevis.network', port=80): Max retries exceeded with url: / (Caused by NewConnec
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:09:16 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-05-10 21:31:58 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-10 21:31:58 UTC → 2026-09-30 16:14:55 UTC · 3,426.72hmidpoint estimate ≈ 2026-07-21 06:53:26 UTC · precision very low · basis bounded
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.
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
