Microsoft Teams help desk impersonation and AD CS abuse
Threat actors are leveraging Microsoft Teams to impersonate support personnel, socially engineering users into granting remote access via Quick Assist to deploy portable runtimes and conduct AD CS abuse (ESC1 and ESC8).
Triage facts
Revision 1- Applicability
- Active Directory Certificate Services, Microsoft Teams +1
- Evidence
- Unknown
- Severity
- High
- Action
- Elevated
- Sources
- 1 public source
- Freshness
- Revision 1Oct 30, 21:17 UTC
- Source quality
- A1Likely
Microsoft observed intrusions where actors used Microsoft Teams to impersonate IT support, gaining interactive access via tools like Quick Assist. Following initial access, actors staged portable runtimes (Python, Bun, Java) in user-writable directories to facilitate host discovery and Active Directory Certificate Services (AD CS) exploitation. Confirmed abuse paths include ESC1 (certificate template misconfiguration) and ESC8 (NTLM relay to AD CS Web Enrollment), the latter involving PetitPotam to coerce authentication.
Attack Chain
- Initial Access: Threat actors use Microsoft Teams to impersonate IT support via messages and calls.
- Execution: The user is socially engineered into initiating a remote support session via Quick Assist.
- Staging: Attackers place a compressed archive into the user's Downloads folder and extract payloads into a 'KB-' prefixed directory under the user profile.
- Runtime Execution: Payloads are executed using portable runtimes (Python, Bun, Java) launched from user-writable locations.
- Discovery: The actor performs internal host and network discovery and evaluates AD CS environments.
- Escalation: Actors perform certificate abuse via ESC1 (template manipulation) or ESC8 (NTLM relay via PetitPotam) to obtain privileged identity certificates.
- Persistence/Exfiltration: Obtained certificates are used for PKINIT or DCSync attacks to further compromise the environment.
Impact
Successful exploitation allows attackers to obtain authentication certificates for privileged identities. These certificates provide durable access independent of user passwords and bypass traditional password reset or workstation re-imaging remediation efforts.
Recommendation
- Audit AD CS certificate templates for ESC1-vulnerable settings (requester-supplied SAN, broad enrollment).
- Implement NTLM relay protections on AD CS Web Enrollment endpoints (e.g., Extended Protection for Authentication).
- Monitor for unusual processes executing from user profile directories (e.g., Python, Java, Bun).
- Configure alerts for atypical AD CS certificate enrollment activity and the use of PetitPotam-related techniques.
- Disable or restrict the use of Quick Assist for users who do not require it for their roles.
- Ensure all service identities and devices are included in automated incident containment policies to prevent exclusion-based persistence.
Immediate actions
Review AD CS template configurations against ESC1 and ESC8 guidance.
Threat Hunt
Hunt for portable runtime execution (Python, Bun, Java) originating from user profile directories.
Data: Process creation logs (Event ID 1)
Mitigations
Enable Extended Protection for Authentication on AD CS Web Enrollment servers.
ESC8 NTLM relay