PhishDestroy identifies Habibi.exchange as an active cryptocurrency drainer phishing domain under investigation for credential theft and fund misappropriation. This fraudulent platform mimics legitimate exchange interfaces to deceive users into surrendering private keys or transferring digital assets to attacker-controlled wallets. The domain is currently unresolved but remains a high-risk threat vector due to its recent creation and suspicious infrastructure alignment with known crypto-phishing campaigns.
This domain was flagged by 0 of 95 VirusTotal vendors as of the investigation seed 7520d9, indicating a low detection rate despite its malicious intent. Habibi.exchange resolves to IP address 108.157.142.92, uses an Amazon-issued SSL certificate for legitimacy deception, and was registered through NameCheap, Inc. on October 20, 2025. The domain exhibits no current blocklist presence, maintaining a deceptive clean record while actively propagating via social engineering vectors. Trust scores remain critically low due to its association with zero vendor detections and freshly minted infrastructure.
Current status remains active with an 'under_investigation' classification, suggesting escalation potential as additional threat intelligence emerges. Users and organizations are advised to block Habibi.exchange at the network perimeter via DNS sinkholing or firewall rules targeting its IP and domain. Immediate reporting to abuse channels such as NameCheap, VirusTotal, and relevant crypto-security forums is recommended to accelerate takedown procedures. Exercise heightened scrutiny for this domain in email campaigns, social media promotions, or unsolicited trading platform invitations, as it continues to pose a credible threat to cryptocurrency holders.
DOM Analysisanalyzed 2026年10月9日score 88/1001 brand signal
Submitted URLhttp://habibi.exchange/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Amazon S3 or Amazon Simple Storage Service is a service offered by Amazon Web Services (AWS) that provides object storage through a web service interface.
Amazon CloudFront is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to customers globally with low latency, high transfer speeds.
Last analyzed First positive detection Previous stored snapshot: 2 detections
Gridinsoft
SOCRadar
网站性能分析
Google PageSpeed Insights — mobile performance audit of habibi.exchange· checked May 4, 2026
44
Poor
Performance
FCP
7.49s
First Contentful Paint
LCP
124.01s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
451ms
Total Blocking Time
SI
43.37s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details1
Availability observations
Last reachable observation
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='habibi.exchange', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
habibi.exchange
Stored observation history12
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
