Security

Passkey Social Engineering Drives Cloud Account Compromise

3 min read

Summary

Microsoft Security Research is tracking active attacks that use passkey, MFA, and SSO-themed social engineering to compromise cloud identities and access Microsoft 365 data. The campaigns rely on AiTM phishing, device code abuse, and unauthorized authentication method changes, making rapid detection and response critical for security teams.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published new research on an active attack pattern that targets cloud identities through passkey-themed social engineering. For IT and security teams, the key takeaway is that these intrusions are not just credential theft events—they often lead to persistent access, Microsoft Graph reconnaissance, and data collection from SharePoint, OneDrive, and Exchange.

What’s happening

Attackers are using phone calls, SMS messages, and sometimes Microsoft Teams messages to impersonate IT helpdesk staff. Victims are told they must urgently update a passkey, MFA, or SSO setting.

Common tactics observed

  • Passkey-themed lures used as a pretext for phishing rather than true passkey enrollment
  • Adversary-in-the-middle (AiTM) phishing to capture credentials and session tokens
  • Device code phishing where users unknowingly authorize attacker-controlled access
  • Unauthorized authentication method changes to establish persistence after sign-in
  • High-volume Microsoft Graph activity for reconnaissance and content discovery
  • SharePoint and OneDrive downloads consistent with targeted data collection
  • Email collection through REST APIs as part of broader cloud compromise

Microsoft notes that attackers often create convincing domains that include the target organization’s name as a subdomain, making the phishing infrastructure look legitimate at a glance.

Why this matters for administrators

This campaign is notable because the initial compromise may leave limited endpoint evidence, especially if the user interacts from a personal mobile device outside managed security tooling. In many cases, the first clue may be a user reporting a suspicious phone call or text.

Security teams should watch for a sequence of events rather than a single indicator:

  • Unusual sign-ins from unmanaged or unfamiliar devices
  • Device code authentication events that do not fit normal user behavior
  • New or unexpected MFA or authentication methods added to accounts
  • Microsoft Graph activity spikes after sign-in
  • Unusual access to SharePoint, OneDrive, Exchange, My Sign-Ins, or My Apps
  • Educate users that IT should not ask them to approve urgent passkey or MFA changes through unsolicited calls or texts
  • Review sign-in logs for anomalous OfficeHome, My Apps, and identity portal access
  • Investigate device code flow usage and token replay indicators
  • Audit recently added authentication methods and remove unauthorized entries
  • Revoke active sessions for confirmed or suspected compromised identities
  • Correlate identity, Graph, SharePoint, OneDrive, and Exchange telemetry during investigations

Bottom line

Microsoft’s research highlights how social engineering can quickly escalate into full cloud account compromise and data exposure. Defenders should focus on detecting the full attack chain—from suspicious sign-ins and MFA persistence to Graph-based reconnaissance and content access—so they can contain incidents before data is exfiltrated.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Microsoft SecurityphishingpasskeysMicrosoft Graphcloud compromise

Related Posts

Security

Microsoft Digital Defense Report 2026: Key Security Insights

Microsoft's 2026 Digital Defense Report highlights how AI and growing system interconnectedness are reshaping both cyberattacks and defense strategies. The report emphasizes that organizations must secure AI, identities, data, and cloud environments together while improving signal correlation across tools to detect modern threats faster.

Security

Government Cyber Risk in 2026: Microsoft’s 5 Priorities

Microsoft says government agencies were the most targeted sector in 2026, accounting for 27% of observed cyber threat activity. The company urges public-sector leaders to focus on five resilience priorities, including faster response, AI security, bidirectional information sharing, and planning for incidents that spread across suppliers and essential services.

Security

Microsoft Ignite 2026 Security Guide: Key Sessions

Microsoft has published its security guide for Microsoft Ignite 2026, highlighting AI-first security themes, a dedicated Security Pre-Day, and technical sessions focused on securing identities, data, devices, clouds, and AI agents. For IT and security teams, the event offers an early look at Microsoft’s roadmap and practical guidance for building an AI-ready security strategy.

Security

CVE-2026-73570: Zimbra Mail Server Exploitation

Microsoft is tracking active exploitation of CVE-2026-73570, an unauthenticated command injection flaw affecting internet-facing Zimbra mail servers with the optional zimbra-snmp package installed and SNMP notifications enabled. The issue can lead to web shell deployment, privilege escalation, mailbox data theft, and persistent remote access, making immediate patching and configuration review critical for administrators.

Security

Phishing Abuses RMM Tools for Persistent Access

Microsoft security researchers observed phishing campaigns in July 2026 that used a legitimate MSP360 RMM installer disguised as meeting invites, PDF updates, and other lures to gain remote access. Attackers then deployed ConnectWise ScreenConnect for redundant persistence, highlighting the need for tighter controls on remote management tools and better detection of unapproved RMM activity.

Security

Azure DevOps Attack Path Exposed in New DART Report

Microsoft’s latest DART cyberattack report shows how a single compromised identity was used to access Azure DevOps, alter pipelines, and harvest Kubernetes credentials. The case highlights how tightly connected identity, DevOps, and cloud environments can let attackers move far beyond source code, making stronger identity and pipeline controls essential.