VirusTotal
6 / 91 engine detections
Open report“Veda | Earn”
The sent-report ledger records the first outgoing report at .
The recorded recipient is compliance@tucows.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
6 / 91 engine detections
Open reportScan report
Open report4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
veda.exchange is a phishing site that impersonates Veda and presents itself under the page title "Veda | Earn" to attract users looking for yield on their crypto. It targets DeFi users and wallet holders who expect a legitimate earning dashboard. PhishDestroy first flagged it on 2026-08-31. The site has been offline since 2026-09-11, and when last checked on 2026-10-19 its content was blocked at the provider level.
Fake "Earn" pages copy the look of a real yield product so that a deposit or vault interface appears trustworthy. The victim is asked to connect a wallet and approve what looks like a routine deposit or staking step. That signature or token approval can give the operator permission to move the victim's assets, and the wallet is emptied without any further action from its owner. Using a .exchange domain under the Veda name adds a layer of legitimacy for anyone who reaches it through a search result, ad or social media link.
On 2026-09-02, VirusTotal showed 6 of 91 engines marking the domain as malicious: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That count is modest, so many security tools would not have warned a visitor at the time. The wallet-focused blocklists matter more here. MetaMask and SEAL both list the domain alongside PhishDestroy, which means wallet users get an in-app warning. Four AlienVault OTX threat pulses also reference it.
The domain was registered through Tucows Domains Inc. on 2025-10-25, about ten months before PhishDestroy detected it. That suggests it was registered well in advance rather than spun up the same day as the campaign. The site sat behind Cloudflare, with the network located in Canada, which hides the origin server. It also used a Google Trust Services certificate, so the padlock in the browser offered no assurance that the site was genuine.
If you connected a wallet to veda.exchange and signed anything, open a token approval manager and revoke every allowance granted to unfamiliar contracts, then move the remaining funds to a fresh wallet. If you entered a seed phrase, treat that wallet as fully compromised and stop using it. Reach Veda only through addresses you have verified independently, never through links. Defenders should block the domain, check DNS and proxy logs for visits since 2026-08-31, and report any lookalike Veda domains that appear.
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-01 04:00:08 UTC
Last checked
For this gTLD, 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 reputation is not attributed to this domain.
bethany.ns.cloudflare.comjustin.ns.cloudflare.comLocation describes the IP network.
50c8c9d19af09a22a64cc8f04a86d8d404428024c419ea35a2c1db41a7c784a6Saved 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 veda.exchange · checked Aug 31, 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
veda.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unavailable→Reachable
Reachable→Unavailable
0→3
Reachable
No threat flag
View source6/91 engine detections
View source4 community references
View sourcePD-20260831-1CAFAD
veda.exchange
View sourcePage captured
View source79 stored lookalike domains
PD-20260831-1CAFAD Recipient: compliance@tucows.com Registrar: Tucows Domains Inc (Canada) Policy Violations: Participates in DNS Abuse Framework; explicitly recognizes phishing, malware, botnets, pharming, spam-as-vector as abuse requiring registrar action Applicable Laws: Criminal Code §342.1 (unauthorized access), §380 (fraud)
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
veda.exchange)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.