VirusTotal
11 / 89 engine detections
レポートを開く“Service Status”
フィッシング: variationsal.io — コンテンツが利用できません. 証拠の概要: VirusTotal 11/89 (ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF); URLScan malicious verdict…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 89 engine detections
レポートを開くDBL_PHISH
悪意あり
レポートを開く3 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
variationsal.io was an impersonation phishing page that presented itself under the bland title "Service Status". It mimicked an official status or verification screen, and urlscan.io matched its look to a generic Cloudflare-style template. It was listed by MetaMask and SEAL, which points to crypto wallet users as the intended audience. PhishDestroy first saw it on 2026-08-14, and the site has been offline since 2026-09-16, with its DNS still inactive as of 2026-10-19.
A "Service Status" page borrows the authority of an infrastructure or platform notice. It typically tells visitors that a service needs attention, a check must be passed, or an account must be re-verified, then steers them to the action the operator wants. On impersonation pages aimed at crypto users, that action is usually entering login details or a recovery phrase, or approving a wallet request. Whatever is handed over goes straight to the attacker.
On 2026-09-15, 11 of 89 VirusTotal engines flagged the domain. The vendors included ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker, Fortinet and G-Data, a mix of crypto-specific and general security vendors. urlscan.io returned a malicious verdict, and Spamhaus lists the domain in its DBL under the phishing category. Alongside PhishDestroy, the MetaMask and SEAL blocklists carry it, and three AlienVault OTX pulses reference it.
The domain was registered through GNAME.COM PTE. LTD. on 2026-08-11, only three days before PhishDestroy detected it. That gap fits a disposable domain stood up for a short campaign. Traffic ran through Cloudflare, Inc. on an address geolocated to Canada, which places the real origin server behind the proxy. The site went dark a day after the last VirusTotal check and did not come back.
If you entered a password on this page, change it right away on the real service and on any account that reuses it, then turn on app-based 2FA. If you typed a seed phrase, treat that wallet as compromised and move your funds to a new wallet with a fresh phrase. If you connected a wallet and signed anything, review and revoke token approvals with a trusted approval checker. Defenders should block the domain at DNS and proxy level and search mail and web logs for visits between 2026-08-11 and 2026-09-16.
Last checked
Edge-IP の評判はこのドメインに起因しません。
kellen.ns.cloudflare.comLocation describes the IP network.
d74b4eb59c45ad78b672583b2909ac9a93b0b216ce3aa1691c5aeaa75aff9814Saved 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.
variationsal.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
blocked→dns_inactive
dns_nxdomain
不明→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
到達可能→利用不可
到達可能
3 community references
View sourceNo threat flag
View source11/89 engine detections
View sourcevariationsal.io
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 ↗
variationsal.io)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.