zkats-brewis.network
“Brevis Campaign”
Evidence Summary
The domain zkats-brewis.network was observed as part of a crypto‑drainer campaign targeting MetaMask users. The site hosted a page titled “Brevis Campaign” and was configured to impersonate the MetaMask wallet interface, a classic vector for wallet/seed phishing. Infrastructure analysis shows the domain is registered through Cloudflare, Inc., and resolves to the IP address 188.114.96.3, which belongs to AS13335 (Cloudflare) located in the United States. No TLS certificate was presented, meaning the site operated over plain HTTP, a detail that can aid traffic‑analysis tools.
The domain employed the publicly known Angel Drainer kit, which is frequently used to exfiltrate private keys and initiate unauthorized cryptocurrency transfers. The site was listed on four independent blocklists—PhishDestroy, Polkadot, Enkrypt, and Codeesura—and appears on additional security blocklists, confirming its malicious reputation. VirusTotal scans returned two positive detections out of ninety‑five vendor engines, and the Gridinsoft trust score was recorded as 0 / 100, indicating an extremely low confidence in safety. The authoritative nameservers are joel.ns.cloudflare.com and nataly.ns.cloudflare.com, consistent with the registrar’s infrastructure.
As of the report date, the domain has been taken offline, but historical records suggest it was actively used in the recent past. Defenders should continue to block the domain and associated IP address, monitor DNS queries for the Cloudflare nameservers, and incorporate the identified kit signature (Angel Drainer) into endpoint detection rules. Adding the domain to internal blocklists and sharing the indicator set with upstream threat‑sharing feeds will help prevent re‑use of the same infrastructure by future campaigns.
Detection timeline
-
Cloudflare Radar
Cloudflare Radar scan stored · Open scan
Threat Response Pipeline
Public Blocklist Status
Blocklist coverage
11 monitored external feeds · stored snapshot Sep 10, 2026
8 monitored external feeds No match
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
VirusTotal Analysis
Evidence & External Reports
Were You Affected by This Site?
If a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive
Recommendations & Advice for Victims
An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with zkats-brewis.network — act now.
What should I do immediately?
Urgent
- Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
- Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
- Change all passwords — email, exchange accounts, anything that shares the same password
- Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
- Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
According to the FBI, the most important details are transaction data:
- Cryptocurrency addresses — scammer's wallet (e.g.,
0x5856...35985) - Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
- Transaction ID (hash) — the unique blockchain transaction identifier
- Exact dates & times — of each transaction and first contact with scammer
- Screenshots — scam website, chat messages, emails, wallet transactions, social media
- All URLs & domains used by the scammer (including
zkats-brewis.network) - Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
- FBI IC3 — Internet Crime Complaint Center (US federal reporting)
- Europol — European cybercrime reporting (EU)
- Chainabuse — flag scam wallets across exchanges & platforms
- Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
- Local police — creates an official record, even if they can't act immediately
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 crypto scams typically work?
- Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
- Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
- Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
- Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
- Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
- AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
- Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
- Bookmark official sites — never click links from emails, DMs, or ads
- Read every approval — verify permissions before signing. Reject unlimited approvals
- Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
- "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines