VirusTotal
1 / 91 engine detections
レポートを開く“Strict CAPTCHA Verification”
偽エアドロップ: wlfiairdropschallenge.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 1/91 (Gridinsoft); 2 external blocklist matches (MetaMask, SEAL)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
1 / 91 engine detections
レポートを開く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
wlfiairdropschallenge.pages.dev is an airdrop scam: a fake token claim page that uses WLFI branding in its name to lure crypto holders with the promise of free tokens. It targets wallet users who hunt for airdrops and are willing to connect a wallet to claim them. PhishDestroy first saw the site on 2026-08-26. It has been offline since 2026-09-01, its content is blocked by the hosting provider, and it was still dead when last checked on 2026-10-19.
Fake airdrop pages promise an allocation of tokens and ask the visitor to connect a wallet and sign a claim transaction. That signature is actually a token approval, a permit or a direct transfer that lets the operator move the victim's assets, so the claim drains the wallet. Some variants also ask for a seed phrase to verify eligibility, which hands over full control of the wallet. The page carried the title "Strict CAPTCHA Verification", which reads like a human-check gate rather than a claim page, while we classify the site as a fake token airdrop.
On VirusTotal, 1 of 91 engines flagged the domain when it was checked on 2026-09-02, and that detection came from Gridinsoft. Detection among general antivirus engines is therefore low. The crypto-focused blocklists are stronger: the domain is listed by PhishDestroy, MetaMask and SEAL, so MetaMask users should see a warning before the page loads.
The site was a subdomain on Cloudflare Pages, with a registration date of 2025-05-11. It resolved to 172.66.46.211 on the Cloudflare, Inc. network, geolocated to CA. Its TLS certificate was issued by WE1, which is standard for this platform and says nothing about legitimacy.
If you connected a wallet or signed anything on this page, open a token approval checker right away, revoke every approval you do not recognize, and move the remaining funds to a fresh wallet. If you typed in a seed phrase or private key, treat that wallet as fully compromised and transfer the assets out from a clean device immediately. Get WLFI airdrop information only from the project's official channels, and ignore claim links that arrive through direct messages or replies. Defenders should block the domain, check for any traffic to it from 2026-08-26 onward, and report new airdrop clones hosted on Pages to the provider and to PhishDestroy.
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 wlfiairdropschallenge.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.
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
wlfiairdropschallenge.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→1
到達可能→利用不可
到達可能
No threat flag
View source1/91 engine detections
View sourcewlfiairdropschallenge.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 ↗
wlfiairdropschallenge.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.