Skip to content

Security Independently confirmed3 publishers 2 min read Published Updated

Storm-3121 callers demand an urgent passkey update to harvest Microsoft 365 session tokens

Microsoft has tracked passkey- and SSO-themed help desk impersonation since May 2026, with the calls steering employees into adversary-in-the-middle proxies and device-code grants that hand over live Microsoft 365 sessions.

The Watch · Security desk

Send a correction

Illustration accompanying Storm-3121 callers demand an urgent passkey update to harvest Microsoft 365 session tokens
Generated illustration

What happened

  • Microsoft has observed the activity since May 2026: attackers research a target company and its staff, then call or message employees while impersonating the corporate IT help desk.
  • The lures centre on passkeys but no passkey enrollment is attempted; the calls exist to move employees into adversary-in-the-middle phishing sites or device-code authentication flows.
  • One investigated session, opened from an unmanaged device, stayed active for roughly an hour while the operator listed sensitive files and internal applications.
  • The crews register domains pairing company names with passkey, SSO, key synchronization, account setup and identity verification wording.

Why it matters

  • What's now possible capability A device-code grant gives the operator a token without harvesting a password and without hosting a fake login page, so domain blocklists and URL-inspection training have nothing to fire on.
  • What it limits constraint Detection has to run on session properties such as the unmanaged device and the order of app access, because the token that arrived had already satisfied MFA and the traffic went to Microsoft's own first-party services.
  • Who's exposed exposure Sending the link by SMS to a personal phone puts the delivery outside the mail gateway and the managed fleet, leaving the sign-in event as the first thing the security team can see.
  • Who has to decide decision Identity teams now have to fix how an employee verifies an unsolicited call about authentication changes, because the attacker's script says what a genuine passkey or MFA notice says.

The device-code path is the one that breaks user training. An employee reads a code back over the phone and types it into Microsoft's own authentication page, and the grant issues a token to an attacker-controlled OAuth application [13][14]. There is no lookalike domain for the employee to check and no password entered into a fake form.

The adversary-in-the-middle path is the older one, and it yields both the password and the session token [11]. Microsoft's write-up of one intrusion shows what the token bought. The sign-in came from an unmanaged device to a service Entra logs as OfficeHome, which covers the Office 365 portal's shared infrastructure and browser-based Office apps [15][16]. The attacker completed MFA, then started checking what the account could reach [17]. Within minutes the session hit My Apps for assigned applications, My Profile, Microsoft Approval Management, account-management interfaces and My Sign-Ins [18]. SharePoint Online, Outlook Web, collaboration and search services, an internal business application and authentication flows tied to virtual desktops followed [19].

Microsoft says the lures frequently revolve around passkeys and that the attackers are not attempting to enroll one [5]. The word is the pretext; the target is a session token or a device-code grant [6]. Microsoft does not say the targeted organizations were running passkey rollouts [24]. What makes the call land is narrower than a rollout schedule: the employee has heard passkey, MFA and SSO from their own IT department, and the caller says their access is about to break [3].

Microsoft published eight example domains, and four of them contain the string passkey: passkeyhelpdesk, secure-passkey, setupmypasskey and add-passkey [25][26]. Two are key-sync constructions, keysyncos and oskeysync, and one, oktasession, names an identity provider that is not Microsoft [25][26]. The victim company's name usually goes in the subdomain, as in company-name.secure-passkey[.]com [10]. On the work that precedes the call, Microsoft wrote: "The actor appears to invest heavily in pre-attack research, likely gathering information about employees and organizational structure from public sources such as social networking and professional profiling platforms" [12].

Microsoft puts the initial access with Storm-3121, which it associates with ShinyHunters and Falcon extortion, and Storm-3032, which it ties to BlackFile members now operating under the Helix name [7][8]. Google Threat Intelligence has tracked overlapping phone-based social engineering and passkey-themed phishing infrastructure as UNC6671 [21]. Google's list of gangs linked to that cluster runs to five: BlackFile, Helix, Falcon, Pink and Redact [22][23].

What to watch

  • Whether Microsoft publishes the OAuth application IDs behind the device-code grants, which would make those grants blockable by tenant policy.
  • Whether the same crews start enrolling their own passkeys on compromised accounts for persistence, instead of only using the word as a lure.
  • Whether the oktasession[.]com-style infrastructure shows the same call script aimed at Okta tenants rather than Entra.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence72
Adoption
Not scored
Hype gap+10
Incentives35
Confidence70

Perspective Coverage

3 publishers
Builder
Builder 25%
Operator
Operator 63%
Investor
Investor 12%
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Microsoft says threat actors linked to ShinyHunters, Helix and other extortion gangs are using passkey and single sign-on-themed social engineering attacks to compromise corporate Microsoft accounts and steal data from Microsoft 365 services.

    Reported SupportedView cited source
  2. [2]

    The activity has been observed since May 2026 and begins with the attackers researching targeted organizations and employees before calling or messaging victims while impersonating corporate IT help desks.

    Reported SupportedView cited source
  3. [3]

    The attackers tell employees that they must urgently update a passkey, MFA or single sign-on configuration to avoid losing access to corporate systems.

    Reported SupportedView cited source
  4. [4]

    Victims are directed to phishing sites designed to resemble legitimate Microsoft login pages, with links sometimes sent through SMS messages to employees' personal phones.

    Reported SupportedView cited source
  5. [5]

    Microsoft says that while the lures frequently revolve around passkeys, the attackers are not attempting to enroll a passkey.

    Reported SupportedView cited source
  6. [6]

    The passkey lures are used to trick targeted employees into signing in to adversary-in-the-middle phishing sites or using device-code authentication flows.

    Reported SupportedView cited source
  7. [7]

    Microsoft attributes the initial-access activity to multiple threat actors operating in the same extortion ecosystem, including groups it tracks as Storm-3121 and Storm-3032.

    Reported SupportedView cited source
  8. [8]

    Storm-3121 is associated with ShinyHunters and Falcon extortion, while Storm-3032 is believed to be tied to BlackFile extortion group members that now work under the Helix name.

    Reported SupportedView cited source
  9. [9]

    The threat actors register phishing domains that combine company names with words related to passkeys, SSO, key synchronization, account setup and identity verification.

    Reported SupportedView cited source
  10. [10]

    The attackers commonly place the victim company's name in a subdomain, such as company-name.secure-passkey[.]com, to make the phishing portal appear more convincing.

    Reported SupportedView cited source
  11. [11]

    AiTM attacks allow the threat actors to capture credentials and session tokens.

    Reported SupportedView cited source
  12. [12]

    "The actor appears to invest heavily in pre-attack research, likely gathering information about employees and organizational structure from public sources such as social networking and professional profiling platforms"

    Reported Supported Source: MicrosoftView cited source
  13. [13]

    Device code phishing tricks victims into authorizing access to their account via an attacker-controlled client using Microsoft's legitimate authentication pages.

    Reported SupportedView cited source
  14. [14]

    In another attack the passkey social engineering led to device-code phishing, where the victim was convinced to enter a supplied code into Microsoft's legitimate authentication page, issuing an authentication token to the attacker-controlled OAuth application.

    Reported SupportedView cited source
  15. [15]

    In one investigated attack, Microsoft observed a suspicious sign-in from an unmanaged device to a Microsoft 365 service identified in Entra logs as "OfficeHome".

    Reported SupportedView cited source
  16. [16]

    OfficeHome is associated with the Office 365 portal's shared infrastructure, including Office applications accessed through a browser.

    Reported SupportedView cited source
  17. [17]

    After completing MFA, Microsoft says the attacker established a valid session and began checking what resources the compromised account could access.

    Reported SupportedView cited source
  18. [18]

    Within minutes, the session was used to access My Apps to see what applications are assigned to the account, My Profile for organizational information, Microsoft Approval Management, account-management interfaces and My Sign-Ins.

    Reported SupportedView cited source
  19. [19]

    The attacker then accessed SharePoint Online, Outlook Web, Microsoft 365 collaboration and search services, an internal business application, and authentication flows associated with virtual desktops.

    Reported SupportedView cited source
  20. [20]

    Microsoft says the session remained active for approximately one hour while the attacker listed sensitive files and internal applications.

    Reported SupportedView cited source
  21. [21]

    The activity overlaps with attacks previously documented by Google Threat Intelligence under the UNC6671 cluster, which Google reported uses phone-based social engineering and passkey-themed phishing infrastructure to compromise corporate identities before accessing enterprise cloud environments.

    Reported SupportedView cited source
  22. [22]

    Google has linked UNC6671 activity to the same extortion gangs, including BlackFile, Helix, Falcon, Pink and Redact.

    Reported SupportedView cited source
  23. [23]

    Google's published list of extortion gangs linked to UNC6671 names five groups.

    Derived Supported
  24. [24]

    Microsoft's account covers the lure, the phishing infrastructure and the post-compromise session, and does not state that the targeted organizations were conducting passkey rollouts at the time.

    Derived Supported
  25. [25]

    Examples seen by Microsoft include passkeyhelpdesk[.]com, secure-passkey[.]com, setupmypasskey[.]com, add-passkey[.]com, integratedsso[.]com, oktasession[.]com, keysyncos[.]com and oskeysync[.]com.

    Reported ContestedView cited source
  26. [26]

    Of the eight example domains Microsoft listed, four contain the string "passkey", two are key-sync constructions (keysyncos, oskeysync), and one names Okta rather than Microsoft (oktasession).

    Derived Contested

Sources

3 independent publishers whose own reporting we read for this story.

  1. bleepingcomputer.com

    1 article · September 11, 2026

    Passkey-themed phishing attacks lead to Microsoft 365 data theft
  2. scworld.com

    1 article · September 15, 2026

    Microsoft warns of cloud storage attacks, financial fraud scams targeting customers
  3. thehackernews.com

    2 articles · September 14, 2026

    Attackers Use Passkey Phishing to Hijack Microsoft Cloud Accounts and Exfiltrate Data

Topics and entities