Executive Summary
In September 2026, Microsoft Security Research documented a sophisticated cloud-based intrusion campaign targeting Microsoft 365 environments through passkey-themed social engineering attacks. Threat actors, including Storm-3121 and Storm-3032, initiated contact via phone calls and SMS messages, directing victims to convincing phishing sites that captured credentials and session tokens through adversary-in-the-middle (AiTM) techniques. Following initial compromise, attackers established persistence by registering unauthorized MFA methods, conducted extensive reconnaissance using Microsoft Graph APIs, and performed high-volume data exfiltration from SharePoint, OneDrive, and Exchange Online repositories over sustained periods spanning hours to days.
This campaign represents a significant evolution in identity-focused attacks, demonstrating how threat actors exploit trust in emerging authentication technologies like passkeys to bypass traditional security controls and establish persistent cloud access.
Why This Matters Now
Identity-based attacks targeting cloud environments have surged 300% in 2026, with passkey-themed social engineering becoming the preferred initial access vector for ransomware groups and data extortion operators seeking to bypass traditional MFA protections.
Attack Path Analysis
Attackers executed passkey-themed social engineering via phone calls and SMS to conduct adversary-in-the-middle phishing, capturing credentials and session tokens. They established persistence by registering attacker-controlled MFA devices, then conducted extensive Microsoft Graph API reconnaissance to map tenant resources. The attackers maintained command and control through rotating proxy infrastructure while conducting automated high-volume data collection from SharePoint, OneDrive, and Exchange using python-httpx tooling. Systematic exfiltration occurred over multiple days with controlled pacing to avoid detection thresholds.
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
Social engineering via phone calls claiming IT helpdesk urgency, directing victims to passkey-themed phishing sites for adversary-in-the-middle credential capture and device code authentication flows
MITRE ATT&CK® Techniques
Phishing for Information: Spearphishing Link
Valid Accounts: Cloud Accounts
Modify Authentication Process: Multi-Factor Authentication
Account Discovery: Cloud Account
Permission Groups Discovery: Cloud Groups
Email Collection
Data from Cloud Storage Object
Exfiltration Over Web Service
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NYDFS 23 NYCRR 500 – Multi-Factor Authentication
Control ID: 500.12
CISA Zero Trust Maturity Model 2.0 – Identity Governance and Administration
Control ID: IM.L2
PCI DSS 4.0 – Multi-factor Authentication for All Access
Control ID: 8.4.2
EU DORA – ICT Risk Management Framework
Control ID: Article 8
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
ISO 27001:2022 – Secure Log-on Procedures
Control ID: A.9.4.2
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Financial Services
Critical exposure to passkey-themed social engineering targeting cloud identities, with high-value financial data accessible through compromised Microsoft Graph reconnaissance and SharePoint exfiltration.
Health Care / Life Sciences
Severe HIPAA compliance risks from identity compromise enabling systematic healthcare data collection through encrypted traffic vulnerabilities and east-west lateral movement attacks.
Information Technology/IT
Maximum impact sector facing multi-stage cloud infrastructure compromise through zero trust segmentation failures, enabling privileged access escalation and multicloud visibility exploitation.
Government Administration
High-priority target for threat actors using device code authentication flows to establish persistence in government cloud environments and exfiltrate sensitive administrative data.
Sources
- Passkey-themed social engineering leads to identity and cloud compromisehttps://www.microsoft.com/en-us/security/blog/2026/09/09/passkey-themed-social-engineering-leads-identity-cloud-compromise/Verified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
- MITRE ATT&CK Framework - Cloud Account Discoveryhttps://attack.mitre.org/techniques/T1087/004/Verified
- Microsoft Graph API Security Best Practiceshttps://docs.microsoft.com/en-us/graph/security-authorizationVerified
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 would likely constrain this Microsoft 365-focused attack by limiting lateral movement paths and reducing blast radius through identity-aware segmentation and controlled egress policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Identity-aware segmentation policies would likely reduce the scope of initial access by constraining which cloud services and resources compromised accounts could reach from external entry points.
Control: Zero Trust Segmentation
Mitigation: Microsegmentation policies would likely constrain the blast radius of compromised accounts by restricting access to sensitive administrative functions and limiting which identity management operations could be performed.
Control: East-West Traffic Security
Mitigation: East-west traffic controls would likely reduce lateral access paths between Microsoft 365 services by enforcing segmentation boundaries that limit cross-service token usage and application-to-application communication flows.
Control: Multicloud Visibility & Control
Mitigation: Centralized visibility controls would likely reduce the effectiveness of rotating proxy infrastructure by providing consistent monitoring and policy enforcement across cloud service interactions and API usage patterns.
Control: Egress Security & Policy Enforcement
Mitigation: Controlled egress policies would likely constrain bulk data extraction by limiting outbound data flows and enforcing transfer restrictions that reduce the volume and scope of automated collection operations.
The scope of compromised data and affected business operations would likely be substantially reduced, limiting the attacker's ability to access critical assets and reducing potential extortion leverage.
Impact at a Glance
Affected Business Functions
- Cloud Identity Management
- Email and Collaboration Services
- Document Management and SharePoint
- Enterprise Data Governance
Estimated downtime: 3 days
Estimated loss: $150,000
Large-scale data exfiltration from Microsoft 365 workloads including SharePoint Online documents, OneDrive business files, and Exchange Online email content. High-volume automated collection spanning multiple user accounts with potential exposure of sensitive organizational data, business communications, and proprietary documents through Microsoft Graph API abuse.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation with identity-based policies to prevent lateral movement between cloud resources and enforce least privilege access controls
- • Deploy Egress Security & Policy Enforcement to detect and block unauthorized outbound data transfers, including python-httpx automation and high-volume API activities
- • Enable Multicloud Visibility & Control with centralized monitoring to detect anomalous Microsoft Graph API reconnaissance patterns and repeated malformed requests
- • Establish Threat Detection & Anomaly Response capabilities to baseline normal user behavior and alert on covert remote access tools like device code flows
- • Enforce Encrypted Traffic controls for all data in transit and implement comprehensive logging of API activities across SharePoint, OneDrive, and Exchange services



