VirusTotal
18 / 92 engine detections
打开报告“wbacq.com”
钓鱼: wbacq.com — 内容不可用. 证据摘要: VirusTotal 18/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Emsisoft); CF Radar malicious; PhishDestroy score 95/100. 注册商…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
18 / 92 engine detections
打开报告恶意
打开报告2 community references
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
wbacq.com is an impersonation phishing site. It presented itself as a legitimate service so visitors would trust it with their credentials or money. PhishDestroy first flagged it on 2026-10-13, and it has been dead since 2026-10-19, with its content no longer reachable. The browser tab showed only the bare domain name, so nothing in the title revealed which service it was copying.
Impersonation pages copy the look and wording of a service the victim already uses, such as a login screen, an account notice or a wallet prompt. They then collect whatever the visitor types. That can be a username and password, one-time 2FA codes, personal details or a wallet recovery phrase. All of it goes straight to the operator, who uses it to take over accounts or empty balances. A forgettable, random-looking name like wbacq.com is typically spread through direct links in messages, ads or DMs rather than found by search.
Independent scanners back our classification. On 2026-10-16, 18 of 92 VirusTotal engines flagged the domain, including BitDefender, Fortinet, Forcepoint ThreatSeeker, Emsisoft, G-Data, alphaMountain.ai, CRDF and CyRadar. Agreement across that many unrelated vendors is a strong signal for a domain this obscure. It also appears in two AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2025-11-25 through Metaregistrar BV, almost eleven months before it came to our attention. That long gap suggests the name was held in reserve or used quietly before this campaign. It was served from Amazon cloud space in the US (AMAZON-AES), which is quick to set up and easy to abandon. Its Sectigo domain-validated certificate gave visitors a padlock icon, but that certificate only proves control of the domain, not the identity of whoever runs it.
If you entered a password on wbacq.com, change it right away on the real service and on any site where you reused it. Enable or reset 2FA, and sign out of all active sessions. If you typed a wallet recovery phrase, consider that wallet compromised and move any remaining funds to a new wallet created from a fresh phrase. Watch your accounts for unfamiliar logins or withdrawals, and report any losses to the service that was impersonated. Defenders should block the domain and its hosting address, and search mail and chat logs for links to it from before 2026-10-19 to find users who may have been exposed.
melissa.ns.cloudflare.comLocation describes the IP network.
fd6b777295029e6aced108e8ee06b1c747bfd8984ac34e2043d53f062713d775webttt555.shopwww.webttt555.shopSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.wbacq.comDomain recordThe original observation time is not recorded for these hostnames.
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.
wbacq.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
可访问→不可用
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
No threat flag
View source18/92 engine detections
View source2 community references
View sourcewbacq.com
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
wbacq.com)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.