basedefi.support is a Coinbase impersonation page detected by PhishDestroy on 2026-04-13. Risk: critical (100/100). Status: Content unavailable. Hosting: Amazon.com, Inc. VirusTotal: 14/94 engines flag it. Do not enter credentials or connect a wallet.
“Coinbase Support | Help Center & Customer Service”
PhishDestroy has flagged www.basedefi.support as a suspected crypto drainer under active investigation. This domain mimics legitimate DeFi support services to trick users into connecting their cryptocurrency wallets under false pretenses. The site leverages social engineering tactics, including impersonation of customer support channels, to convince victims to authorize malicious transactions that drain funds directly from their wallets. Security researchers have observed similar campaigns targeting users of decentralized finance protocols, where attackers pose as support agents and guide victims to interact with fraudulent smart contracts that siphon assets. The domain is not yet widely blocklisted, making it a high-risk vector for unsuspecting users seeking assistance with DeFi platforms. This domain resolves to IP address 216.198.79.1 and is secured with a Let's Encrypt SSL certificate, which may give it an appearance of legitimacy to non-technical users. VirusTotal currently shows 0 detections out of 95 security engines, indicating that mainstream antivirus and threat intelligence platforms have not yet flagged it as malicious. The domain is associated with a registrar that has been linked to multiple fraudulent activities in the past, though its creation date has not been publicly disclosed. At the time of this assessment, the domain remains active and operational, with no visible takedown efforts by hosting providers or law enforcement. Given the lack of detections and the sophisticated nature of crypto drainer operations, this domain poses a significant and evolving threat to users in the DeFi space. If you have visited www.basedefi.support, immediately disconnect your wallet from the site and revoke any unauthorized permissions using tools like Revoke.cash or Etherscan’s token approval checker. Do not interact with any prompts or transactions suggested by the site, as these are likely designed to steal your assets. Scan your device for malware or browser extensions that may have been compromised during the visit. Report the domain to PhishDestroy for further analysis and consider warning others in your network who may have been targeted. For future interactions with DeFi platforms, always verify official support channels through the project’s official website or verified social media accounts to avoid falling victim to similar scams.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
No. PhishDestroy classifies basedefi.support as a Coinbase impersonation page (risk: critical, 100/100); it was first detected on 2026-04-13. VirusTotal: 14/94 engines flag it. Treat the site as unsafe.
Is basedefi.support safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on basedefi.support. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used basedefi.support?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedApr 13, 2026
DOM Analysisanalyzed Jul 29, 2026score 73/1003 brand signals
Submitted URLhttps://www.basedefi.support/
Case ID
Observed page title
Coinbase Support | Help Center & Customer Service
Automated brand references
AcrossCoinbaseCoinbase Wallet
TLS Certificate
Issued by Let's Encrypt· stored validity ends in 89 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
216.198.79.1
Network ASN
AS16509
Organization
Lefkoff Industries
Observed location
Atlanta, US
Server header
Vercel
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-04-13 15:45:08
Valid until
2026-07-12 15:45:07
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-05-26 05:00:10 UTC
Collection source
PhishDestroy collector
Certificate names · 1 SAN
www.basedefi.support
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-21 01:12:16 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-05-26 22:09:37 UTCcurrent episode first observed: 2026-09-30 16:26:51 UTCobserved RIP window: 2026-05-26 22:09:37 UTC → 2026-09-30 16:26:51 UTC · 3,042.29hmidpoint estimate ≈ 2026-07-29 07:18:14 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 2 identified
V
Vercel
PaaSCDN
Cloud platform for frontend deployment, optimized for Next.js.
H
HSTS
Security
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google PageSpeed Insights — mobile performance audit of basedefi.support· checked Apr 13, 2026
59
Needs Work
Performance
FCP
3.52s
First Contentful Paint
LCP
5.33s
Largest Contentful Paint
CLS
0.205
Cumulative Layout Shift
TBT
6ms
Total Blocking Time
SI
5.38s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
3042.29
Estimate basis
Bounded by observations
Estimate precision
very_low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='basedefi.support', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
basedefi.support
Saved result
Unreachable
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · basedefi.support
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
7 evidence signal groups linked0 stored notification recordsContent unavailable
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including basedefi.support)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
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.
