VirusTotal
6 / 92 engine detections
打开报告冒充 Across Protocol: aevos-protocol.net — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 6/92 (Abusix, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft)…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 92 engine detections
打开报告Suspicious
打开报告3 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
aevos-protocol.net is an impersonation phishing site whose name is built to pass as an official domain for a crypto protocol. It targets DeFi users and wallet holders who arrive through search results, social media links or direct messages. PhishDestroy first flagged it on 2026-10-06, and as of 2026-10-19 the site is still online, with its content sitting behind a protection layer.
Impersonation pages like this copy a protocol's look and wording, then push the visitor toward a single action. That action is usually connecting a wallet and signing a transaction or token approval, or typing a recovery phrase into a fake "restore" or "verify" form. Either one hands the operator control of the victim's funds. The page title currently reads "Just a moment...", which is a browser-check interstitial rather than branded content, while our classification is based on the impersonation scheme behind it.
Six of 92 VirusTotal engines flagged the domain as of 2026-10-10: Abusix, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a low count, but these vendors work independently, and early-stage phishing domains often show this pattern before wider coverage catches up. The domain appears in three AlienVault OTX threat pulses, so other researchers are tracking it as well. Among blocklists, PhishDestroy currently lists it.
The domain was registered on 2026-09-24, just 12 days before PhishDestroy detected it, which fits the short lifespan typical of phishing campaigns. It is registered through Cloudflare, Inc. and served from Cloudflare's network (AS13335) in the US, so the origin server's real location is hidden behind the proxy. Its free Let's Encrypt certificate means the padlock in the browser says nothing about whether the site is legitimate.
If you connected a wallet to this site, use a token-approval checker to revoke any permissions you granted. Then move remaining assets to a new wallet. If you entered a seed phrase or private key, treat that wallet as compromised and transfer everything to a freshly generated wallet immediately, because revoking approvals will not protect it. Only reach the real protocol through its verified official channels and bookmarks. Defenders should block aevos-protocol.net at DNS and proxy level, look for lookalike domains containing the same name, and report it to Cloudflare's abuse team for takedown.
Edge-IP 声誉不属于此域。
rob.ns.cloudflare.commx1.hostinger.compriority 5mx2.hostinger.compriority 10Location describes the IP network.
47c6aaa3947f16e27cf914c01e082e16f5a108b57a9dd47373196064f37deb31Saved 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 aevos-protocol.net · checked Oct 6, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
No threat flag
View source6/92 engine detections
View source3 community references
View sourceaevos-protocol.net
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
aevos-protocol.net
Listed 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 ↗
aevos-protocol.net)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.