VirusTotal
15 / 95
“Predictive AI Agents for Advanced Financial Intelligence”
The domain ozak.claims has been identified as posing a high risk due to its classification as a crypto drainer threat. Currently, the domain is offline, but it previously impersonated the brand 'across' with a page titled 'Predictive AI Agents for Advanced Financial Intelligence'. This suggests a sophisticated attempt to deceive users into compromising their cryptocurrency wallets.
Data analysis reveals that the domain is flagged by 15 out of 95 security vendors on VirusTotal, indicating significant detection of malicious activity. The domain was registered through NET-USA under ASN 400992 and resolved to IP address 185.245.34.139 located in the United States, specifically under AS400992 ZhouyiSat Communications. The SSL certificate used is a Let's Encrypt certificate with identifier E7, and the site appears on two known security blocklists. These details underscore the potential threat posed by this domain.
Currently, ozak.claims is offline, reducing immediate risk. However, users should remain vigilant and avoid any engagement with similar domains or sites that utilize Wallet Connect Abuse drainer kits. Security measures such as utilizing browser extensions that block known phishing sites can help prevent exposure. Continuous monitoring of security blocklists for updates and employing strong authentication methods are recommended to safeguard against such threats.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0xC73a02c63277fC12F28Ae6D78bD7E1B6b425911BFormat validated · Domain analysishttps://t.me/OzakAGIStored page referenceIoC extraction recorded 2026-08-02 04:25:16 UTC
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ozak.claims', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<S
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.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
3dc46073dee0a4adc75587d38334cc7626c4b26701d25a324c2cd189674b2f84Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
15 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.
Reported by 1 community member, first seen Nov 17, 2025
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.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with ozak.claims — act now.
According to the FBI, the most important details are transaction data:
0x5856...35985)ozak.claims)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.