Microsoft Details Teams Intrusions Abusing AD CS Certificate Weaknesses

· Original article ↗

Summary

Microsoft investigated two intrusions that began with attackers posing as IT support on Teams and abusing insecure AD CS configurations. In one, company data was copied to an external server; the amount was not disclosed.

Key points

  • In both intrusions, attackers posed as company IT or help desk staff on Teams and persuaded employees to give them control through Windows Quick Assist.
  • In one intrusion, attackers abused an ESC1 certificate template to obtain certificates for privileged accounts, then used DCSync; Microsoft did not say how much credential data was obtained.
  • An account excluded from automatic containment remained usable, allowing the attacker to access a file server and use Rclone to copy company data to an external SFTP server. The amount copied was not disclosed.
  • In the second intrusion, attackers used PetitPotam to coerce domain-controller authentication, relayed it to AD CS web enrollment through ESC8, and obtained a certificate for the domain controller.
  • Microsoft said isolating the workstation in the second intrusion stopped further activity; in the first, Defender blocked many attempts but did not contain every privileged identity.
  • Microsoft says certificates issued through misconfigured templates can remain usable after a password reset or machine wipe. EPA is enabled by default for AD CS in Windows Server 2025, while Server 2022 and 2019 require manual enablement.
  • Microsoft provided Defender alerts and four advanced hunting queries as investigation starting points, not proof on their own.

Article Details

Attack Vectors
  • Attackers impersonated company IT or help-desk staff in Microsoft Teams messages and calls, persuading employees to open Quick Assist and share its connection code.
  • After gaining workstation control, attackers dropped and unpacked an archive, then ran its contents using a portable Python, Bun, or Java runtime.
  • In one intrusion, attackers abused an ESC1 AD CS certificate template to request certificates representing privileged accounts, then used a certificate to access a domain controller and run DCSync.
  • In the other intrusion, attackers used PetitPotam to coerce a domain controller into authenticating to an attacker-controlled machine, relayed the NTLM authentication to AD CS web enrollment (ESC8), and requested a certificate for the domain controller.
  • An attacker used a privileged account excluded from automatic containment to access a file server and copy data from a share to an external SFTP server using a renamed copy of Rclone.
Defensive Notes
  • Review AD CS certificate-template configuration and address ESC1 exposure; secure AD CS web enrollment against ESC8 relay abuse.
  • Enable Extended Protection for Authentication (EPA) for AD CS. Microsoft said it is enabled by default for AD CS in Windows Server 2025, while Windows Server 2022 and 2019 require manual enablement.
  • Ensure identity containment covers every affected privileged account. Microsoft reported that an excluded account remained usable after other identities were disrupted.
  • Isolate affected workstations when warranted; Microsoft said workstation isolation stopped further activity in the second intrusion.
  • Treat password resets and wiping the first machine as insufficient to invalidate an already-issued certificate, according to Microsoft.
  • Microsoft described its advanced hunting queries as starting points for investigation, not proof on their own.

MITRE ATT&CK

Vendors

Products

Tools

Related Articles