1-minute read
What a defender needs to know
Cisco Talos traced mid-2026 event invitations aimed at people affiliated with Taiwan research organizations to a spoofed Google login. The emails borrowed real event details and institution names, but their registration links led to phishing infrastructure. Some attached posters carried altered QR codes, so a forwarded or printed poster could bring another person to the same lure.
The phishing page sent browser information, account identifiers, passwords and challenge submissions to the actor’s server through HTTP POST. A persistent WebSocket carried updates back to the page as the server followed Google’s sign-in steps. Talos says the kit could collect authenticated session tokens. Its assessment of AI-assisted invitation writing is based on repeated language and personalized templates; use the link and QR destinations for routing checks.
Preserve the invitation’s real link target and decode the poster QR destination in a controlled workflow. Match visits with web records and the affected user’s Google security events. Block verified phishing destinations and alert the event organizer about altered posters. If a user entered credentials or a challenge, have them use a trusted route to review Recent security events, managed devices, recovery settings and Gmail forwarding rules; change their Google password if another person may be signed in. Verify that the registration URL points to the organizer’s page and that device and account settings reflect the owner’s actions. A quiet signature feed cannot replace the account check.