VirusTotal
14 / 91 engine detections
Mở báo cáo“首页”
Giả mạo Binance: vbyyuk.christmas — Chưa được xác minh. Tóm tắt bằng chứng: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLQuery 1…
Phân tích chi tiết của PhishDestroy AI bên dưới được giữ bằng tiếng Anh để bảo toàn hồ sơ pháp chứng gốc.
14 / 91 engine detections
Mở báo cáo1 threat-system alert
Mở báo cáoĐộc hại
Mở báo cáoĐộc hại
Mở báo cáo5 community references
Mở báo cáoNo threat flag
Mở báo cáoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | www.vbyyuk.christmas |
malicious | Sinkholed |
PhishDestroy threat report
Analysis of www.vbyyuk.christmas indicates an active high‑risk brand‑impersonation campaign targeting Binance. The domain was registered on July 5 2026 through Spaceship, Inc. and resolves to IP 47.242.217.10, which is assigned to AS45102 (Alibaba (US) Technology Co., Ltd.) and geolocated to Hong Kong. Nameservers launch1.spaceship.net and launch2.spaceship.net are consistent with the registrar. The web server reports HTTP 200 and presents a page titled “首页”, while no TLS certificate is deployed, leaving the connection unencrypted. Infrastructure fingerprints show Nginx serving the site and a client‑side Vue.js framework, a combination frequently observed in modern phishing kits.
VirusTotal scans have flagged the domain by 7 of 91 security vendors, and the domain appears on one public blocklist and is already listed by PhishDestroy. The site’s declared scam type is “Brand Impersonation” and the target brand is Binance, confirming the intent to deceive users of that cryptocurrency exchange. Evidence beyond the page title is not yet publicly available; the exact content, login forms, or credential‑harvesting mechanisms have not been captured. Defenders should immediately block the domain and its hosting IP at perimeter and DNS layers, add the nameservers to watchlists, and monitor for additional domains registered through the same registrar or using the same AS.
Continuous re‑scanning with multi‑engine services is recommended to capture any changes in detection scores. Given the lack of TLS, any traffic to the site can be intercepted, but the primary risk remains credential theft through a likely counterfeit Binance login page. Organizations with Binance accounts should warn users to verify URLs and enforce multi‑factor authentication. Threat intelligence feeds should be updated with the indicator set (domain, IP, ASN, registrar) to improve early detection of related campaigns.
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.
launch1.spaceship.netlaunch2.spaceship.netLocation describes the IP network.
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.
vbyyuk.christmas
5 community references
View source14/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcevbyyuk.christmas
View source187 tên miền tương tự đã lưu
Hiển thị 100 trong tổng số 187
Listed domains receive at least one abuse report; this entry has no retained notification history.
Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
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 ↗
vbyyuk.christmas)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
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
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
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.