VirusTotal
0 / 89 engine detections
レポートを開く“Desktop Browser Required”
block-noise-28.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 0/89; PhishDestroy score 53/100. レジストラ: Cloudflare Pages.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
0 / 89 engine detections
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
block-noise-28.pages.dev was a short-lived impersonation phishing page hosted on a free Cloudflare Pages subdomain and aimed at crypto users. PhishDestroy flagged it on 2026-09-13, the same day the site was created. It went offline on 2026-09-20 and was still down and blocked by the hosting provider when last checked on 2026-10-19.
The page greeted visitors with the title "Desktop Browser Required", a device-check message rather than a recognizable brand name, while we classified the site as impersonation. Impersonation pages copy the look of a trusted wallet, exchange or service so that victims believe they are on the real thing. Once that trust is in place, the victim is asked to log in, enter a recovery phrase, or connect and approve a wallet. Whatever is entered goes to the operators, and that can mean a hijacked account or an emptied wallet.
Independent detection was essentially absent. VirusTotal returned 0 detections out of 89 engines on 2026-09-19, six days after the site appeared, and PhishDestroy is the only blocklist carrying it. A clean scan result here reflects how quickly throwaway pages outpace vendor feeds, not that the site was safe. The provider's later block of the content backs the classification.
The operators used a pages.dev subdomain with a disposable-looking name. They needed no domain purchase or registrar paperwork, and the page could go live within minutes. It sat on Cloudflare, Inc. address space geolocated to Canada and served a Google Trust Services certificate. That certificate comes automatically with the platform, so the padlock said nothing about the site's legitimacy. The page lasted about a week, from 2026-09-13 to 2026-09-20, which is typical of hit-and-run campaigns that burn one subdomain and move to the next.
If you typed a password or one-time code into this page, change that password right away. Do the same on any account that reuses it, and reset two-factor authentication if the codes may have been captured. If you entered a seed phrase, treat the wallet as compromised and move any remaining funds to a new wallet created on a clean device. If you connected a wallet and signed anything, review and revoke token approvals with a reputable approval checker. Defenders should block the domain and watch for similar randomly named pages.dev subdomains that use device-check lures like this one.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
f685272edd02e580d26d77151d654a5a108ece2d1358aaa5a63c6a0f42b05440Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
block-noise-28.pages.dev
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
到達可能→利用不可
到達可能
0/89 engine detections
View sourceNo threat flag
View sourceblock-noise-28.pages.dev
View sourceListed 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 ↗
block-noise-28.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.