Microsoft Threat Intelligence said on November 5, 2026 that since August it has seen threat actors use an agentic AI offensive framework to search public GitHub repositories for credentials, application credentials and AI inference API keys, then use them for further malicious activity against victim organizations [1]. Microsoft says it observed successful service principal sign-ins from a specific IP since October 28 involving multiple applications at some customers, including a vendor-owned multitenant app credential stolen at the source and used against multiple downstream tenants, and iThome reports one case went from searching GitHub to exfiltrating data from Azure Key Vault in five minutes [1][2]. Microsoft advises organizations to scan their GitHub code for secrets and immediately rotate any exposed keys or credentials, since exposed credentials stay usable until revoked or rotated and deleting the original disclosure does not fix it [1].
Attackers use AI agents to sweep GitHub for leaked secrets and abuse service principals to break into Azure tenants
1 min read
- Disclosed
- Nov 5, 2026
- Published
- Nov 12, 2026
- Last updated
- Nov 12, 2026
- CVSS basis
- Our assessment
- Technology
- Attack vector
- Impact
- Data type
- Actor type
- Motivation
- MITRE ATT&CK
On this page
30-second summary
What happened
Who is affected
Industries mainly affected: Cross-industry
What to do nowOur advice
Microsoft advises organizations to scan their GitHub code for secrets and immediately rotate any exposed keys or credentials, since exposed credentials stay usable until revoked or rotated and deleting the original disclosure does not fix it
Timeline
Technical details
Remediation
Vendor guidance
- 1Rotate exposed secrets mitigate[1]
Scan your GitHub code for secrets and immediately rotate any exposed keys or credentials.
- 2Enable public monitoring detect[1]
Enable GitHub public monitoring to detect secrets leaked to other public repositories.
- 3Review workload identity permissions verify[2]
Review past use of exposed credentials and confirm service principals are not over-privileged.
References
Official / primary1
- [1]Microsoft Threat Intelligence2026-11-05Accessed 2026-11-12Snapshot 2026-11-12 sha256 fd5177f6a6b1
“Publicly exposed credentials remain usable until revoked or rotated; removing the original disclosure alone does not remediate the exposure.”
Media1
- [2]
This site aggregates public information and is not security consulting advice. Test remediation steps before applying.