AEGLIX News
In late October 2026, Push Security identified and stopped visits to malicious event registration pages. The operation relies on counterfeit invitations that mimic OpenAI, SpaceX, and Anthropic gatherings to harvest Microsoft and Google account credentials along with active authentication sessions. Although the initial distribution method for the phishing links remains unknown, Push Security observed that the attackers route victims to the fraudulent registration page through shortened URLs from trusted providers such as Google and Zapier.
The same phishing pages incorporate both the Kali365 and VoidProxy phishing-as-a-service platforms. Kali365 is used to carry out Microsoft device code phishing, while VoidProxy functions as an adversary-in-the-middle reverse proxy that intercepts Google sign-ins and captures authentication session cookies. In the Microsoft-focused flow, VoidProxy serves as a second stage, seizing credentials and session cookies after Kali365 has obtained authentication tokens. Analysts assess that the same threat actors are behind both the ZoomMock and MSDRoot kits, citing shared infrastructure and overlapping targeting patterns.
Threat actors employ custom phishing kits tracked as ZoomMock and MSDRoot to build the bogus event pages. One page advertises an OpenAI event titled ChatGPT for Social & Digital Marketing Teams that promises three months of ChatGPT Pro. Another page promotes a private SpaceX event scheduled for November 12, offering either three months of Grok Heavy or a SpaceX share. A third page, which impersonated an Anthropic event at AWS re:Invent 2026, has already been taken down. The counterfeit registration pages display a Cloudflare CAPTCHA to hinder automated security scanners from analyzing the phishing site.
Push Security detected and blocked visits to the malicious event registration pages in late October 2026. Additionally, the phishing page that impersonated an Anthropic event at AWS re:Invent 2026 has already been removed.
Report prepared 2026-11-05 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.
Sources
Read original source · BleepingComputer (opens in a new tab)