Executive Summary
In mid-2026, a threat actor tracked as UAT-11985 launched a sophisticated spear-phishing campaign targeting individuals affiliated with Taiwan research organizations. The operation used AI-assisted content generation to craft convincing fake event invitations impersonating legitimate academic and policy institutions, including the Taiwan European Union Centre and NCCU Institute of International Relations. Victims were lured to an adversary-in-the-middle (AitM) phishing framework that spoofed Google login pages, harvesting credentials and MFA codes in real time via obfuscated JavaScript and WebSocket connections. The campaign also embedded malicious QR codes into legitimate event posters to extend the attack surface beyond email recipients.
This incident reflects a broader and accelerating trend of AI-augmented phishing operations targeting geopolitically sensitive organizations. The combination of AitM proxy techniques, MFA bypass, and QR code phishing (quishing) represents a significant evolution in credential theft tradecraft, making traditional perimeter defenses and user awareness training insufficient on their own.
Why This Matters Now
AI-generated spear-phishing now enables threat actors to produce high-volume, highly personalized lures at scale, effectively nullifying the traditional 'spot the typo' defense. With MFA no longer a reliable last line of defense against AitM attacks, organizations must enforce network-level controls, egress filtering, and zero-trust segmentation to detect and contain credential-harvesting infrastructure before account takeover completes.
Attack Path Analysis
UAT-11985 launched AI-assisted spear-phishing emails impersonating Taiwan academic and policy institutions, embedding deceptive URLs and malicious QR codes to lure targets to an adversary-in-the-middle (AitM) phishing framework that harvested Google credentials and MFA codes in real time. The stolen session tokens enabled full Google account takeover, with the attacker leveraging WebSocket-based C2 infrastructure to exfiltrate credentials covertly, ultimately compromising research-affiliated accounts and enabling downstream intelligence collection against Taiwan-linked organizations.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
UAT-11985 sent AI-generated spear-phishing emails to Taiwan research affiliates, impersonating legitimate institutions such as the Taiwan European Union Centre and NCCU Institute of International Relations. Emails contained hyperlinks masquerading as Google Forms URLs and embedded malicious QR codes on scraped event posters, directing victims to attacker-controlled AitM phishing infrastructure mimicking Google login panels.
MITRE ATT&CK® Techniques
Phishing: Spearphishing Attachment
Phishing: Spearphishing Link
Adversary-in-the-Middle
Steal Web Session Cookie
Phishing for Information: Spearphishing via QR Code
Impersonation
Establish Accounts: Social Media Accounts
Exfiltration Over C2 Channel
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev. 5 – Authenticator Management, Identification & Authentication, Transmission Confidentiality
Control ID: IA-5, IA-8, SC-8
CISA Zero Trust Maturity Model 2.0 – Phishing-Resistant MFA and Continuous Identity Validation
Control ID: Identity Pillar – Visibility & Analytics (Level 2-3), Device Pillar – Device Compliance
NIS2 Directive (EU) 2022/2555 – Incident Handling, Access Control, and Supply-Chain Risk
Control ID: Article 21(2)(a), 21(2)(i) – Risk Management & Supply-Chain Security
GDPR (EU) 2016/679 – Integrity & Confidentiality, Security of Processing, Breach Notification
Control ID: Article 5(1)(f), Article 32, Article 33
ISO/IEC 27001:2022 – Secure Authentication Controls and Security Awareness Training
Control ID: A.8.5 (Secure Authentication), A.8.23 (Web Filtering), A.6.1 (Information Security Awareness)
DORA (EU) 2022/2554 – ICT Risk Management and Incident Classification
Control ID: Article 9 – ICT Security, Article 17 – ICT-Related Incident Management
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Higher Education/Acadamia
Taiwan research affiliates face AitM credential theft via fake academic event invites, requiring Zero Trust Segmentation and Egress Security to prevent real-time Google account takeover and MFA bypass.
Government Administration
Impersonation of policy institutions in spear-phishing lures exposes government-affiliated personnel to credential harvesting, demanding Multicloud Visibility and encrypted traffic controls aligned with NIST.800-53.SC-12.
Information Technology/IT
AitM phishing infrastructure using obfuscated JavaScript and WebSocket C2 exfiltration targets IT environments, requiring Cloud Firewall egress enforcement and Inline IPS to disrupt real-time credential relay.
Research Industry
AI-generated spear-phishing targeting Taiwan research organizations exploits institutional trust; East-West Traffic Security and Zero Trust Segmentation are critical to contain post-compromise lateral movement per ZTMM.Network compliance.
Sources
- UAT-11985 Uses Fake Event Invites to Target Taiwan Research Affiliates With Google AitM Phishinghttps://thehackernews.com/2026/10/uat-11985-uses-fake-event-invites-to.htmlVerified
- Cisco Talos Intelligence Blog: UAT-11985 Campaign Analysis by Joey Chenhttps://blog.talosintelligence.com/uat-11985/Verified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
- MITRE ATT&CK: Phishing for Information (T1598)https://attack.mitre.org/techniques/T1598/Verified
- MITRE ATT&CK: Adversary-in-the-Middle (T1557)https://attack.mitre.org/techniques/T1557/Verified
- Google Security Blog: Protecting Against Phishing and Account Takeoverhttps://security.googleblog.com/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is relevant to this incident because UAT-11985 exploited uncontrolled outbound access and unrestricted lateral paths across cloud-hosted Google Workspace environments to harvest credentials and pivot across institutional research accounts. By enforcing identity-aware segmentation, controlled egress, and east-west traffic policies, Aviatrix would likely reduce the reachability of attacker-controlled infrastructure and constrain how far compromised session tokens could propagate across connected cloud resources.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Outbound connections from cloud-hosted workloads toward attacker-controlled AitM phishing domains would likely be constrained, reducing the reachability of spoofed login infrastructure from within the research organization's cloud environment and limiting how effectively the phishing redirection chain could be completed through managed network paths.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation would likely reduce the scope of what an attacker could access using a stolen session token by constraining authenticated sessions to identity-scoped network segments, meaning that even a valid token may not grant unrestricted reachability across all cloud-hosted resources the victim account is associated with.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement would likely constrain the attacker's ability to move laterally between cloud-hosted workloads or shared research environments using a compromised session, reducing the number of reachable internal resources available to an attacker operating through a single hijacked account.
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility across outbound traffic flows would likely surface anomalous WebSocket connections and repeated HTTP POST activity toward attacker-controlled endpoints, potentially reducing the attacker's ability to maintain persistent covert C2 channels through cloud-egress paths that are subject to traffic inspection and policy enforcement.
Control: Egress Security & Policy Enforcement
Mitigation: Egress policy enforcement would likely reduce the attacker's ability to exfiltrate harvested credential and session data over unsanctioned outbound channels, constraining the effectiveness of split-channel exfiltration designs that rely on unrestricted HTTP and WebSocket egress paths from within the cloud environment.
Where prior CNSF controls reduced lateral reach and constrained egress, the remaining impact would likely be scoped to the directly compromised accounts rather than spreading broadly across affiliated institutional environments, reducing the blast radius from organization-wide intelligence collection to a more limited subset of exposed research content.
Impact at a Glance
Affected Business Functions
- Academic and Policy Research Operations
- Institutional Email and Collaboration Systems
- Multi-Factor Authentication and Identity Management
- Sensitive Government and Cross-Border Research Communications
Estimated downtime: N/A
Estimated loss: N/A
The campaign is specifically designed to harvest Google account credentials and real-time MFA authentication tokens from individuals affiliated with Taiwan-based research and academic institutions, including the Taiwan European Union Centre, NCCU Institute of International Relations, and Taiwan Research Institute. Data at risk includes: full Google account access enabling exfiltration of sensitive research correspondence, geopolitical policy documents, inter-institutional communications, conference materials, and personally identifiable information of researchers and policy professionals. The AitM proxy achieves full account takeover without victim awareness, meaning the scope of data accessible post-compromise extends to all Google Workspace assets including Drive, Gmail, Calendar, and Meet. Secondary victims may also be affected through QR code phishing embedded in physical printed event materials, broadening the compromise surface beyond direct email recipients. Given the geopolitical focus on Taiwan-EU and Taiwan-China policy research, the intelligence value of the harvested accounts is assessed as high, with potential nation-state espionage implications.
Recommended Actions
Key Takeaways & Next Steps
- • Deploy Cloud Native Security Fabric (CNSF) inline enforcement to detect and block outbound WebSocket and HTTP POST connections to unknown or newly registered domains, specifically targeting the real-time credential-relay pattern used by AitM phishing kits before session tokens are exfiltrated.
- • Enforce Egress Security & Policy Enforcement (FQDN filtering and outbound traffic controls) to prevent workloads and user endpoints from reaching attacker-controlled phishing infrastructure, blocking the AitM relay domains at the network layer even when URLs superficially resemble legitimate Google Forms endpoints.
- • Apply Multicloud Visibility & Control to baseline normal authentication traffic patterns and flag anomalous interactions such as simultaneous WebSocket connections to non-Google domains during Google login flows, enabling detection of AitM proxying activity through traffic observability and centralized policy alerting.
- • Implement Zero Trust Segmentation with identity-based policy to enforce least-privilege access boundaries on compromised research accounts, limiting lateral movement across Google Workspace services and shared institutional resources even after valid session tokens are obtained by the attacker.
- • Leverage Cloud Firewall (ACF) with AI-assisted traffic discovery and URL filtering to identify and block access to spoofed Google login panels and quishing-linked domains, reducing the attack surface for both email-delivered URLs and QR-code-redirected traffic targeting Chinese-speaking research affiliates.



