bitgetwallet.com.cn impersonates Bitget’s wallet service to steal crypto. Resolves to 156.234.3.94, registered May 2026. Avoid this domain immediately.
PhishDestroy identifies bitgetwallet.com.cn as an active brand impersonation domain targeting Bitget users. The domain mimics Bitget’s wallet service to deceive victims into entering credentials or transferring cryptocurrency. Current status remains under investigation as analysts assess its operational scope and potential impact.
This domain was flagged by 1 of 95 VirusTotal vendors, indicating it currently evades widespread detection despite its malicious intent. Registered through 成都西维数码科技有限公司 on May 02, 2026, it resolves to IP 156.234.3.94 and utilizes a Let’s Encrypt SSL certificate for a false sense of legitimacy. The domain exhibits no current blocklist presence and maintains low trust scores across threat intelligence platforms, suggesting it is a newly deployed operation with limited exposure thus far.
Users are strongly advised to avoid interacting with bitgetwallet.com.cn and report any encounters to Bitget’s official support channels. Organizations should consider blocking the domain at the network perimeter and monitoring for related infrastructure. Given the domain’s recent registration and low detection rates, heightened vigilance is critical to prevent credential theft or financial loss. Bitget users should verify wallet access exclusively through the official bitget.com domain or its authenticated applications.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-213161.invalid', port=80): Max retries exceeded with url: / (Caused by
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.
Certificate fingerprint89b19ce3afaa9e87ebdef641d45777eb19f175b328ab5e19efdb75ce3476c381Certificate names · 1 SANs
bitgetwallet.com.cn
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:31:41 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-23 02:12:50 UTC
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.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-213161.invalid· checked May 3, 2026
76
Needs Work
Performance
FCP
3.78s
First Contentful Paint
LCP
4.31s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.04s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-25 01:31:11 UTC
Domain state transitioned from alive to dead.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
