okxpay[.]my

PhishDestroy first observed okxpay.my on Aug 31, 2026. The hostname explicitly references OKX; stored content metadata identifies the same apparent target. Current evidence score: 66/100 (high).

Positive findings are stored from 2 sources: MetaMask and SEAL. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 31, 2026 at 18:20 UTC. Non-positive and contextual checks: VirusTotal recorded 0 detections among 91 engines on Aug 31, 2026 at 18:40 UTC. AlienVault OTX listed 2 community pulse references (not vendor detections) on Aug 31, 2026 at 20:24 UTC. URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Aug 31, 2026 at 20:23 UTC. URLScan captured the page on Aug 31, 2026 at 18:32 UTC. The 0/91 VirusTotal snapshot and the positive findings above are conflicting observations from different sources or collection times.

The collector marked the hostname reachable on Aug 31, 2026 at 18:32 UTC, but did not retain the HTTP response code. Registration records for the domain list Gname.com Pte. Ltd. as the registrar and Aug 28, 2026 as the creation date. Registration preceded first observation by 3 days. At collection time, the hostname resolved to 188.114.97.3. The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists Google Trust Services as the certificate issuer with validity through Nov 27, 2026; checked Aug 31, 2026 at 19:02 UTC.

The content indicators and 2 positive source findings support the current OKX impersonation and phishing classification. The target field identifies OKX, but the record does not establish whether the page requested credentials, a seed phrase, or a wallet connection.