VirusTotal
15 / 89 engine detections
PhishDestroy first recorded ouyi.systems on 2026-03-31. Stored VirusTotal result: 15/89 engines flagged.
Page title: “Earn rewards when you get started on OKX | My referral code: 92497733 | OKX United States”
Stored VirusTotal result: 15/89 engines flagged. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
PhishDestroy analysis, earlier unreviewed version
PhishDestroy identifies ouyi.systems as an active crypto drainer domain, posing a high risk to users' cryptocurrency assets. This domain is under investigation for phishing activities specifically targeting crypto wallet credentials and transaction approvals. The site leverages deceptive tactics to trick users into connecting wallets or signing malicious transactions, leading to irreversible fund losses. Technical analysis confirms the domain is operational and distributing malicious payloads, with no current detections on VirusTotal as of the latest scan.
This domain was flagged by PhishDestroy due to its suspicious behavior and lack of legitimate indicators. ouyi.systems resolves to IP 54.215.31.113, registered through Dynadot Inc on October 02, 2025. The domain uses a Let's Encrypt SSL certificate to appear legitimate, though this is a common tactic among malicious actors. As of now, VirusTotal reports 3/95 detections, indicating it has evaded initial detection by antivirus engines. The domain's recent creation date and hosting infrastructure further contribute to its high-risk classification. Trust scores and blocklist entries are pending further investigation, but preliminary data suggests a strong likelihood of malicious intent.
To mitigate risks associated with this crypto drainer, users must avoid interacting with ouyi.systems entirely. If you've already visited the site, disconnect your wallet immediately and revoke any connected permissions via your wallet's settings. Scan your device for malware using reputable security tools like Malwarebytes or Windows Defender. Report the domain to PhishDestroy and your browser's safe browsing program to help block future access. Always verify URLs manually and use hardware wallets for transactions to minimize exposure to drainer scripts. Stay vigilant—crypto drainers often mimic legitimate platforms to exploit user trust.
15 / 89 engine detections
3 threat-system alerts
Open report1/100
Trust score, lower = worse
Open reportMalicious
Open report23 community references
Open reportScan report
Open report98 / 100 · heuristic score · 4 brand references · 1 classification
Content heuristic only; not the final score
Open reportNarrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Private YARA rules | static.okx.com/cdn/assets/okfe/util/ont/5.8.45/ont.js | audit | Hunting_JS_WebAssembly |
| Hagezi Threat Feed | www.zhgwexpouy.net | malicious | Sinkholed |
| DNS4EU | www.zhgwexpouy.net | malicious | Sinkholed |
PhishDestroy rates ouyi.systems as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-03-31. Stored VirusTotal result: 15/89 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on ouyi.systems. A confirmed blockchain transaction cannot be reversed.
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
5b6fb45a30e7a0c4c82631f662dcaffb5ac13bfc0a45cbd37e9480ee96fe1e80 · 148617 bytes b74fe8d97f32d41b17d69ce5da49dbf9592d240466c9e8e75a984a3e81098cdc · 51365 bytes 
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.
ns1.dyna-ns.netns2.dyna-ns.netLocation describes the IP network.
47fc3a02595757109f2e4df79e817853f067618746cca50bee281c4e968b4ecd33593.cc937913.comabbasitvhd.comanimze.netarunainfoco.comdesi49.bizhondamc2011.comlfav95.ccsmileuniverse.onlinespeedone.com.bdthekella.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The domain no longer resolves in DNS.
Google PageSpeed Insights — mobile performance audit of ouyi.systems ·
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 231 SHA-256 hashes: 198 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 04:56 UTC.
Open this scan on URLScan 019d44f1-dd47-73de-9918-798733c2fab4 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
dns_nxdomain: no HTTP response; DNS NXDOMAIN recorded 2026-11-12 10:22:07.093838
ouyi.systems Source: domain_monitor. This stored snapshot does not establish current availability.
Recorded events: 16. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 180 d 2 h after registration
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
89 stored lookalike domains
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
Where to send it:
Nothing matches. Clear the search or choose another filter.
Showing 12 of 89
Reported by 1 community member, first seen 2026-03-31
PD-20260331-77232F Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
ouyi.systems)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.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
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.