VirusTotal
2 / 89 engine detections
レポートを開く“JUST A PSYOP”
ブロックリスト掲載ドメイン: fgfggreerferf.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 2/89 (alphaMountain.ai, Gridinsoft); 1 external blocklist match…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 89 engine detections
レポートを開く15/100
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開く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
fgfggreerferf.pages.dev is an impersonation phishing page hosted on a throwaway Cloudflare Pages subdomain whose random-keystroke name was clearly never meant to be remembered. It targets crypto users by posing as a service they already trust. PhishDestroy first flagged it on 2026-09-05. The site has been offline since 2026-09-16, its content was blocked by the provider, and it was still dead when last checked on 2026-10-19.
Impersonation pages copy the look of a familiar wallet, exchange or project and steer visitors into an action that hands over control, such as typing a seed phrase or password or approving a wallet request. Whatever is entered or signed goes straight to the operator, and stolen crypto is usually moved out within minutes. The page carried the title "JUST A PSYOP," which names no brand, while our analysis classified the content as impersonation phishing.
Independent detection was thin. When scanned on 2026-09-17, only 2 of 89 VirusTotal engines (alphaMountain.ai and Gridinsoft) flagged the site. A clean result from most engines is common for fresh pages.dev phishing and does not mean the site was safe. Stronger support comes from ScamSniffer, a blocklist focused on crypto wallet scams, which listed the domain alongside PhishDestroy.
The subdomain was created on 2026-09-04 and detected the next day, which is typical of disposable phishing builds that go live and get reported almost immediately. It ran on Cloudflare's network with a Canada geolocation, and the free hosting made it easy to spin up and abandon. Its Google Trust Services certificate was issued automatically by the platform, so the browser padlock said nothing about who ran the page. The page lasted about twelve days before the provider blocked it.
If you entered a seed phrase or private key on this page, treat that wallet as compromised and move any remaining funds to a new wallet with a fresh phrase from a device you trust. If you connected a wallet and signed anything, check its token approvals with a revocation tool and cancel any you don't recognize. If you typed an exchange or account password, change it and reset two-factor authentication on that account. Security teams should block the domain and watch for similar random-string pages.dev subdomains, because operators tend to reuse this pattern after a takedown.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
7c55466686da79c1503865ab5dfd156d29af80009e87a7d7a482f7a1f591ca5cSaved 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
fgfggreerferf.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
到達可能→利用不可
到達可能
No threat flag
View source2/89 engine detections
View sourcefgfggreerferf.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 ↗
fgfggreerferf.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.