VirusTotal
16 / 91
flare-gov.network — 未验证 (HTTP 409). 品牌冒充:MetaMask; 诈骗类型:Impersonation. 证据摘要: VirusTotal 16/91 (ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF); Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. 注册商: NiceNIC.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
flare-gov.network is an active high‑risk domain that has been observed in a generic phishing campaign targeting government‑related email addresses. The domain was registered on June 06, 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED and resolves to the Cloudflare‑owned address 172.67.140.131. Within weeks of creation the domain appeared on three independent security blocklists, and three commercial filtering services—PhishDestroy, MetaMask, and SEAL—have added it to their deny lists.
VirusTotal has recorded detections from 16 of 91 scanned engines, indicating that a notable portion of the security community considers the site malicious. The rapid appearance on blocklists and the multi‑engine detections suggest that the infrastructure is being used to host phishing pages or to redirect victims to credential‑harvesting sites, although the exact content of the landing page has not been publicly disclosed. The use of a Cloudflare IP provides the attacker with DDoS protection and potential anonymity, making takedown more challenging.
Defenders should block any outbound connections to 172.67.140.131, add flare‑gov.network to internal URL filtering lists, and monitor for authentication attempts against government portals that originate from this host. Incident response teams should also consider the domain when investigating recent credential‑theft alerts, and threat‑intel feeds should be updated to reflect the current detection status. Further analysis of HTTP responses, SSL certificates, and page titles is required to confirm the exact phishing payload and to identify any additional infrastructure linked to this campaign.
针对该主机的爬虫与浏览器观察记录,以及针对“Keitaro”式流量分配系统的实时指纹检测。
cloudflare扫描说明: empty_body: raw=empty_body; http=409; via=http_proxy; server=cloudflare
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP 声誉不属于此域。
Location describes the IP network.
a3310216df39d809d077dd2afcd2cf77f51e9afc4c6273750abdddf0a2cbfd3cSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
172.67.140.131. 12 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
已存储 79 个仿冒域名
由 1 名社区成员报告;首次发现于 2026年6月7日
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent