VirusTotal
12 / 91 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
dYdXなりすまし: feat-edit-competition.dydx-trading-competition-frontend-production.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 12/91 (ADMINUSLabs…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 91 engine detections
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This Cloudflare Pages subdomain poses as the frontend of a dYdX trading competition. Its name copies the style of a developer preview build, aimed at dYdX traders who expect a legitimate event page. PhishDestroy first flagged it on 2026-08-26. The site has been offline since 2026-09-01, and Cloudflare was still blocking its content when last checked on 2026-10-19.
Trading-competition lures promise leaderboard prizes or bonus rewards. To join, the visitor is asked to connect a wallet and sign transactions, which can hand an attacker spending rights over their tokens. Some versions ask for a recovery phrase instead, which gives away the whole wallet. The page title now reads "Suspected Phishing | Cloudflare", Cloudflare's own warning screen, so visitors today see that interstitial rather than the dYdX imitation we classified.
On 2026-09-02, VirusTotal showed 12 of 91 engines flagging the domain. They include crypto-focused ChainPatrol alongside mainstream vendors ESET, BitDefender, Fortinet, G-Data, alphaMountain.ai, CyRadar and ADMINUSLabs. That count is modest, but it is backed by MetaMask's and SEAL's blocklists as well as PhishDestroy's. Two independent crypto-security lists agree with us, so the classification rests on more than one verdict.
The operator never registered a domain. They deployed onto Cloudflare's free Pages platform, which serves the site from Cloudflare, Inc. address space with a Canadian geolocation. Using a pages.dev subdomain lets a phishing site borrow a trusted parent name at no cost. The deliberately long, build-like name helps it pass a quick glance in a link preview. Cloudflare's block followed within days of our first sighting.
If you connected a wallet here, review and revoke any token approvals or permits granted around 2026-08-26 and after. Then move remaining funds to a fresh wallet. If you typed a recovery phrase, treat that wallet as fully compromised and stop using it. Reach dYdX competitions only through dYdX's official channels, and distrust preview-style pages.dev links shared in chats or replies. Defenders should block this hostname, watch for similarly named Pages subdomains referencing dYdX, and report new ones to Cloudflare and SEAL.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of feat-edit-competition.dydx-trading-competition-frontend-production.pages.dev · checked Sep 1, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
到達可能
No threat flag
View source12/91 engine detections
View sourcefeat-edit-competition.dydx-trading-competition-frontend-production.pages.dev
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
feat-edit-competition.dydx-trading-competition-frontend-production.pages.dev
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose 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 ↗
feat-edit-competition.dydx-trading-competition-frontend-production.pages.dev)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.