VirusTotal
16 / 89 engine detections
打开报告“Veda | Earn”
钓鱼: app.veda.exchange — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 16/89 (alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft); Spamhaus DBL_PHISH; PhishDestroy…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
16 / 89 engine detections
打开报告DBL_PHISH
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
app.veda.exchange is on the PhishDestroy blocklist. It presented itself under the title "Veda | Earn", which uses the Veda name and an earning or yield theme aimed at crypto users. PhishDestroy first saw it on 2026-09-02. The site has been offline since 2026-09-25, its content was blocked by the provider, and it was still down at the last check on 2026-10-19.
The site has no PhishDestroy scheme classification, so the risk comes from its branding and from how outside vendors flagged it. An "Earn" page under a recognizable DeFi name invites visitors to connect a wallet or deposit funds in exchange for promised yield. Spamhaus files the domain under phishing. On a page like this, any wallet connection, transaction signature or deposit should be treated as potentially giving control of funds to whoever runs the site.
On 2026-09-11, 16 of 89 VirusTotal engines flagged the domain. The vendors included alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet and G-Data. That is a moderate but solid count, and it comes from several unrelated security companies rather than a single source. The Spamhaus Domain Block List lists the domain in its phishing category, which supports PhishDestroy's own listing.
The domain was registered through Tucows Domains Inc. on 2025-10-25, about ten months before PhishDestroy detected it. Because it sat unused for that long, the registration date alone would not have looked suspicious. The site resolved to Cloudflare, Inc. infrastructure, with the network located in Canada. This means the IP address belongs to the proxy and does not reveal the real origin server. The site went offline roughly three weeks after it was first seen.
If you connected a wallet to this site, review your token approvals with a trusted approval-checking tool and revoke any you do not recognize. If you signed anything you were unsure about, move your remaining assets to a fresh wallet. If you deposited funds, do not pay any further "unlock" or "withdrawal" fees, because these payments do not bring money back. Keep your transaction hashes and report the incident. Defenders should block app.veda.exchange at DNS and proxy level, alert users about lookalike Veda earning pages, and watch for the same branding appearing on new domains.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/+GfI_iZQ6wsZlZWNhStored page referenceIoC extraction recorded 2026-09-03 04:00:10 UTC
For the registrable domain veda.exchange behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP 声誉不属于此域。
bethany.ns.cloudflare.comLocation 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 app.veda.exchange · checked Sep 2, 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
app.veda.exchange
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
可访问→不可用
8→16
4→8
3→4
可访问
No threat flag
View source16/89 engine detections
View sourceapp.veda.exchange
View sourcePage captured
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 ↗
app.veda.exchange)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.