Join our Newsletter — 33% off our NHI Course
Home› Guides› Silk Typhoon Threat Actor Profile Guide: From Exchange…
Guide Threat Intelligence & Threat Actors

Silk Typhoon Threat Actor Profile Guide: From Exchange Exploits to Stolen API Keys

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 12 min read
On this page

Silk Typhoon, the group Microsoft first named HAFNIUM, has moved from mass exploitation of on-premises Exchange servers to stealing the API keys and application credentials of IT service providers and using them to walk into downstream customer tenants. That shift turns a supplier's non-human identities into a route into your environment, often without a single phishing email or failed logon. This profile covers the group's names, targeting, the ATT&CK techniques documented against it, how it abuses service principals, OAuth apps and vaulted secrets, and what identity, cloud and SOC teams should monitor and change. It is for defenders running Microsoft 365 and Entra ID, organisations that rely on PAM, remote support or cloud data management vendors, and threat intelligence teams building hunts.

Key takeaways

  • Same group, two eras. In 2021 HAFNIUM exploited four Exchange Server zero-days (the ProxyLogon chain); by 2025 Microsoft reported Silk Typhoon abusing stolen API keys and credentials from IT supply chain companies.
  • Your supplier's keys are your attack surface. Microsoft describes the group stealing keys from privileged access management, cloud application and cloud data management providers, then reaching those providers' customers.
  • Applications are the persistence layer. The group adds its own credentials to already-consented apps, abuses multi-tenant apps and creates apps with names that blend in, then reads mail and files through Microsoft Graph and EWS.
  • Edge zero-days and n-days still open the door. Ivanti Connect Secure, PAN-OS GlobalProtect and Citrix NetScaler flaws appear alongside password spraying and passwords leaked on GitHub.
  • Detection depends on workload identity telemetry. Service principal sign-in logs, app credential changes and Graph activity are where this actor shows up; many tenants do not collect or review them.

Who they are (names and aliases)

MITRE ATT&CK tracks the group as G0125 HAFNIUM, with associated names HAFNIUM, Operation Exchange Marauder and Silk Typhoon, and describes it as a likely state-sponsored cyber espionage group operating out of China. Microsoft introduced HAFNIUM on 2 March 2021, assessing with high confidence that it was behind the Exchange zero-day campaign, and renamed it Silk Typhoon when it moved to its weather-based naming scheme (Typhoon denotes China-based actors). In a March 2025 post Microsoft said it had tracked the group since 2020.

On 19 July 2021 the United States, with allies, publicly attributed the Exchange compromises to cyber actors affiliated with China's Ministry of State Security, as recorded in CISA advisory AA21-062A. Other vendors use their own names for overlapping activity, and overlaps are imperfect: treat any mapping as approximate. See the Threat Actor Naming Conventions Guide and the China State Cyber Operations Guide for how this group sits alongside Volt, Salt and other Typhoons.

Targeting and motivation

The motive is intelligence collection. Microsoft's 2021 report listed infectious disease researchers, law firms, higher education, defence contractors, policy think tanks and NGOs, primarily in the United States, and noted that the group operated from leased virtual private servers in the US. ATT&CK's description adds a broad set of US sectors.

The 2025 reporting describes a change of method rather than of goal. Microsoft observed Silk Typhoon going after IT providers, remote monitoring and management tools and cloud applications to gain access to many customers at once, and reported victims including state and local government and the IT services sector. For defenders, this means your exposure depends on the security of every vendor holding a key or app registration into your tenant, which is a third-party risk question as much as a SOC one. See the Cybersecurity for MSPs and MSSPs Guide.

Tactics and techniques (MITRE ATT&CK)

The table maps techniques ATT&CK v20 attributes to G0125 (plus one mapping of Microsoft's description, marked) to the procedure reported. It is not exhaustive.

TacticTechniqueDocumented procedure
ReconnaissanceT1593.003 Search Open Websites/Domains: Code RepositoriesSearched GitHub for leaked corporate passwords
Resource developmentT1584.005 Compromise Infrastructure: BotnetCovert networks of compromised devices (Microsoft cites Cyberoam, Zyxel and QNAP) to hide origin
Initial accessT1190 Exploit Public-Facing ApplicationExchange ProxyLogon chain; Ivanti, PAN-OS and NetScaler vulnerabilities
Initial accessT1199 Trusted RelationshipStolen API keys and credentials of PAM, cloud app and data management providers used against downstream customers
Credential accessT1110.003 Password SprayingSpraying cloud accounts
Credential accessT1555.006 Cloud Secrets Management StoresRead passwords from Azure Key Vault
Credential accessT1003.003 OS Credential Dumping: NTDSDumped Active Directory
PersistenceT1505.003 Web ShellChina Chopper, ASPXSpy and others on Exchange servers
PersistenceT1053.005 Scheduled Task, with S1011 TarraskHidden scheduled tasks
PersistenceT1098 Account Manipulation; T1136.002 Domain AccountReset default admin passwords; created domain accounts
Persistence (writer mapping)T1098.001 Additional Cloud CredentialsMicrosoft: added credentials to already-consented applications
Lateral movement, accessT1078.004 Cloud Accounts; T1550.001 Application Access TokenAbused service principals and app tokens to reach data
CollectionT1114.002 Remote Email Collection; T1530 Data from Cloud StorageExported mailboxes through Microsoft Graph; took OneDrive and SharePoint content
ExfiltrationT1567.002 Exfiltration to Cloud StorageUploaded data to MEGA
Defence impairmentT1685.005 Clear Windows Event LogsCleared logs after activity

Vulnerabilities associated with the group

CVEProductNatureAdded to CISA KEV
CVE-2021-26855Exchange ServerServer-side request forgery, first link of ProxyLogon3 November 2021
CVE-2021-26857Exchange ServerInsecure deserialisation in the Unified Messaging service3 November 2021
CVE-2021-26858, CVE-2021-27065Exchange ServerPost-authentication arbitrary file write3 November 2021
CVE-2023-3519Citrix NetScaler ADC and GatewayCode injection19 July 2023
CVE-2024-3400Palo Alto Networks PAN-OSCommand injection12 April 2024
CVE-2025-0282Ivanti Connect Secure, Policy Secure, ZTA GatewaysStack-based buffer overflow8 January 2025

Microsoft listed the 2023 to 2025 CVEs among those the group exploited; the KEV dates show when CISA confirmed exploitation in the wild by anyone, not when Silk Typhoon first used them.

How they abuse identities and credentials

This is where the profile matters most for identity teams. Microsoft's 2025 reporting describes a chain that rarely touches a human password once the group is inside.

  • Supplier key theft: the group compromised IT providers and took API keys and credentials that those providers use to manage their customers. A key built to reset passwords or pull data across many tenants becomes a multi-victim initial access token. See the API Key Management Guide.
  • Vault harvesting: ATT&CK records reads from Azure Key Vault, and Microsoft reports the group stealing passwords held in vaulting products. A vault is only as safe as the identities allowed to read it.
  • Hybrid identity pivots: Microsoft reports targeting of Microsoft Entra Connect (formerly AAD Connect) servers, which hold the synchronisation account bridging on-premises AD and the cloud. See the Microsoft Entra Connect and Cloud Sync Hardening Guide.
  • Application credential backdoors: adding a client secret or certificate to an app that already holds admin consent gives silent, MFA-free access with the app's permissions. Creating new apps named to look like legitimate tooling, and abusing multi-tenant apps, extends the same idea. See the Entra ID Applications and Consent Guide.
  • App-only data access: with application permissions such as Mail.Read or Files.Read.All, Graph and EWS let an attacker read every mailbox or drive in scope. Activity appears as service principal sign-ins, not user sign-ins.
  • Leaked and sprayed passwords: GitHub searches and spraying supply the first foothold where no vulnerability is available. See the Password Spraying and Credential Stuffing Defence Guide.

The pattern overlaps with the key theft covered in the Storm-0558 and Cloud Key Theft Profile, but where Storm-0558 forged tokens with a stolen signing key, Silk Typhoon mostly uses keys and app credentials that were legitimately issued and then stolen. Rotation, scoping and ownership of those credentials are the controls that matter.

Notable incidents

  • Exchange ProxyLogon campaign (2021): Microsoft disclosed on 2 March 2021 that HAFNIUM was exploiting four zero-days in on-premises Exchange to steal mailbox data and plant web shells. CISA's AA21-062A told organisations to investigate from 1 January 2021 and, where exploitation was found, to assume the network identity had been compromised. Exploitation by other actors followed quickly once the flaws were public.
  • IT supply chain campaign (reported March 2025): Microsoft described stolen keys from PAM, cloud app and cloud data management companies used to access downstream customer environments, followed by app abuse and Graph exfiltration.
  • The PAM vendor key pattern in practice: the BeyondTrust breach of December 2024 shows exactly this risk: a stolen Remote Support SaaS API key able to reset local application passwords was used against customers including the US Treasury, which attributed the intrusion to a China state-sponsored actor. Treasury's statement did not name a specific group, so treat it as an illustration of the technique, not an attribution.

Detection and defence

What to monitor

SignalWhere to find itWhy it matters
New client secret or certificate on an existing app or service principalEntra ID audit log ("Update application, Certificates and secrets management", "Add service principal credentials")Primary persistence method described by Microsoft
Service principal sign-ins from new IPs, regions or hosting rangesEntra ID service principal sign-in logsApp-only access does not appear in user sign-in logs
New app registrations or consents to high-privilege Graph permissionsEntra ID audit log, consent eventsApps named to blend in with legitimate tooling
Bulk mailbox or file reads by an appMicrosoft Graph activity logs, unified audit log (MailItemsAccessed)Collection through Graph and EWS
Reads from key vaults by unusual identitiesAzure Key Vault diagnostic logsT1555.006 vault harvesting
Exchange exploitation artefactsHttpProxy logs with empty AuthenticatedUser and AnchorMailbox like ServerInfo~*/*, ECP logs showing Set-*VirtualDirectory with script, new .aspx files in aspnet_client or owa\authIndicators Microsoft published for ProxyLogon
Security event log clearingWindows Event ID 1102, System Event ID 104T1685.005

Hardening priorities

  1. Inventory every external key and app: list all vendor API keys, service principals, multi-tenant apps and delegated admin relationships with access to your tenant, with an owner and a business purpose for each. See the GDAP and MSP Delegated Admin Access Guide.
  2. Cut app-only permissions down: Microsoft recommends reviewing application permissions and using RBAC for Applications in Exchange Online to scope mail access to specific mailboxes rather than the whole tenant.
  3. Apply Conditional Access to workload identities: restrict where single-tenant service principals can sign in from and alert on risky service principal sign-ins.
  4. Harden hybrid identity: treat Entra Connect servers as Tier 0 and avoid on-premises accounts holding cloud admin roles, as Microsoft advises.
  5. Patch internet-facing appliances against KEV: where a listed CVE was exposed before patching, hunt for compromise; patching alone does not remove a web shell or a stolen key.
  6. Rotate and scope vendor keys: require IP allow-listing, expiry and least privilege on keys you issue to suppliers, and contract for prompt notification of key compromise.

Response

If you find a malicious credential on an app, remove it, rotate every secret on that app, review all permissions it holds and search Graph and audit logs for its activity back to the start of retention. If a supplier reports key theft, revoke the key, reset anything the key could reset, and review access from that supplier's identities. See the OAuth Token Theft Incident Playbook, the Web Shell Response Playbook and the Supply Chain Compromise Response Playbook.

Metrics

  • Owned workload identities: percentage of service principals and vendor keys with a named owner and review date.
  • Credential age: number of app secrets older than your rotation policy, and number of apps holding more than one active secret.
  • High-privilege app permissions: count of apps with tenant-wide Mail, Files or Directory write permissions, tracked downward.
  • Telemetry coverage: service principal sign-in and Graph activity logs collected and retained for at least the period your investigations need.
  • KEV exposure time: days from KEV listing to patch for internet-facing appliances.

Framework mapping

Defensive needNIST SP 800-53 Rev. 5NIST CSF 2.0
Inventory and lifecycle of workload identities and keysAC-2 Account Management, IA-5 Authenticator ManagementPR.AA-01
Least privilege for app permissionsAC-6 Least PrivilegePR.AA-05
Supplier access and key handlingSA-9 External System Services, SR-3 Supply Chain Controls and ProcessesGV.SC-07
Edge vulnerability managementRA-5 Vulnerability Monitoring and ScanningID.RA-01
Monitoring of sign-ins and app activitySI-4 System Monitoring, AU-6 Audit Record ReviewDE.CM-01

Practitioner checklist

  • Export every service principal and app registration with credentials, permissions, owner and last sign-in; disable those without an owner.
  • Alert on any new secret or certificate added to an existing application, and on new consents to Graph application permissions.
  • Collect service principal sign-in logs and Microsoft Graph activity logs into your SIEM.
  • Scope Exchange Online app access with RBAC for Applications instead of tenant-wide Mail permissions.
  • List every vendor that holds an API key or delegated admin access to you, and confirm rotation, IP restriction and breach notification terms.
  • Treat Entra Connect servers and key vaults as Tier 0 and restrict who can read vault secrets.
  • Patch the CVEs in the table above on any internet-facing system and hunt where exposure preceded patching.
  • Scan your public code repositories for leaked credentials and rotate anything found.
  • Run a tabletop on "a supplier tells us its API key into our tenant was stolen".

Standards and references

Related NHI Mgmt Group resources: Storm-0558 and Cloud Key Theft Profile · Azure RBAC and Service Principals Guide · SaaS and OAuth App Governance Guide · Volt Typhoon Threat Actor Profile · Compromised MSP Playbook

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.