VirusTotal
14 / 89 engine detections
打开报告“Service Status”
钓鱼: vasriational.io — 内容不可用 (HTTP 403). 证据摘要: VirusTotal 14/89 (ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF); URLScan malicious verdict…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
14 / 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
vasriational.io is an impersonation phishing page aimed at cryptocurrency users. urlscan.io matched it to a generic crypto brand rather than a single named project. The page presented itself under the title "Service Status". PhishDestroy first flagged it on 2026-08-14, and the site has been dead since 2026-09-16, with its DNS still inactive when we last checked on 2026-10-19.
Fake status pages work by manufacturing urgency. They announce an outage, a pending migration or a sync error, then offer a "fix" that requires connecting a wallet, signing a transaction or typing in a recovery phrase. Any of those steps can hand an attacker control of the funds. A signed approval lets them drain tokens, and a seed phrase gives them the whole wallet. The bland "Service Status" title does not by itself name a brand, but we classified the domain as impersonation based on the detections below.
Independent signals back the classification. On 2026-09-15, 14 of 89 VirusTotal engines flagged the domain, among them crypto-focused ChainPatrol along with alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, Forcepoint ThreatSeeker and Fortinet. urlscan.io returned a malicious verdict. Spamhaus lists it in its DBL as phishing, and it appears on the MetaMask and SEAL blocklists. Wallet-side blocking from MetaMask and SEAL matters most here, because it can warn users at the moment they try to connect. Three AlienVault OTX threat pulses also reference the domain.
The domain was registered through GNAME.COM PTE. LTD. on 2026-08-11, only three days before PhishDestroy caught it. That short gap is typical of throwaway phishing domains built for a short campaign. It sat behind Cloudflare's network, with the serving address geolocated to Canada, so the true origin server stays hidden. The site went offline on 2026-09-16, about a month after detection.
If you connected a wallet to this site, review and revoke any token approvals or permissions you granted, and move funds to a fresh wallet if you signed anything you did not understand. If you entered a seed phrase or private key, treat that wallet as compromised and transfer remaining assets to a new wallet created on a clean device right away. Real projects never ask for a recovery phrase to resolve a service issue. Defenders should keep vasriational.io blocked in DNS filters and secure web gateways, and search proxy logs from 2026-08-11 onward for users who reached it.
Last checked
Edge-IP 声誉不属于此域。
kellen.ns.cloudflare.comLocation describes the IP network.
6ef11c15b384dda4f2ab7c306e4c83519f6a72670c2ca3c34dc142cc6b0902f5Saved 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
vasriational.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
可访问→不可用
1→14
可访问
3 community references
View sourceNo threat flag
View source14/89 engine detections
View sourcevasriational.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 ↗
vasriational.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
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.