Analysis of shardssoniclabs.online indicates a high‑risk crypto drainer campaign targeting WalletConnect users. The site was registered on 21 October 2025 through IONOS SE and resolves to IP 75.2.60.5, an Amazon Web Services host in the United States (ASN 16509). No TLS certificate is presented, meaning traffic is unencrypted.
The HTTP response is currently unavailable because the domain has been taken offline, but historical observations recorded the page title “Sonic Shards,” which aligns with the advertised drainer kit identified as “Wallet Connect Abuse.” The domain’s authoritative name servers are ns1070.ui‑dns.biz, ns1093.ui‑dns.com, ns1100.ui‑dns.de, and ns1113.ui‑dns.org, a pattern previously seen in other cryptocurrency‑drainer infrastructure. Reputation checks show a Gridinsoft trust score of 0 / 100 and a VirusTotal detection rate of 13 out of 95 scanning engines flagging the domain as malicious. The site appears on two public blocklists – PhishDestroy and ScamSniffer – and has been classified as a “Crypto Scam” that impersonates the legitimate WalletConnect brand.
Given the combination of low trust rating, multiple vendor detections, and confirmed impersonation of a cryptocurrency wallet service, defenders should immediately block the domain and its associated IP address at perimeter and DNS layers. Security teams should also add the four UI‑DNS name servers to watch lists, monitor for newly‑registered domains using the same registrar or similar naming patterns, and update intrusion‑detection signatures to detect the “Wallet Connect Abuse” kit behavior. Continuous threat‑intel feeds should be consulted for any resurgence, and any endpoints that may have communicated with the domain should be examined for credential leakage or unauthorized wallet transactions.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/Sonic_EnglishStored page reference
IoC extraction recorded 2026-08-02 04:28:24 UTC
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='shardssoniclabs.online', port=80): Max retries exceeded with url: / (Caused by NewConnecti
DOM Analysisanalyzed 2026年4月23日score 93/1001 brand signal
IoC Extractionscanned 2026年8月2日0 wallet · 1 Telegram IoC
Submitted URLhttp://shardssoniclabs.online/
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:10:05 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-03 10:24:21 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-03 10:24:21 UTC → 2026-09-30 16:14:55 UTC · 2,861.84hmidpoint estimate ≈ 2026-08-02 01:19:38 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.
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.
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.
您的加密货币交易所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
加密货币诈骗通常是如何运作的？
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
恶意批准 — “连接钱包”的提示会使攻击者获得无限的代币消费权限
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
(DE)
