AI agent finds leaked GitHub key and empties cloud vault in 5 minutes
Hackers are using AI agents to scan GitHub for leaked keys and steal cloud data in minutes. Deleting the code is no longer enough.
Tools · Source: Microsoft Security Blog
What happened
Hackers are deploying AI agents to hunt for your mistakes. Microsoft just caught threat actors using an AI framework called ARTEX to scan public GitHub repositories. These agents look for exposed passwords, API keys, and application credentials. Searching open code repositories for exposed credentials is an old tactic. But in the past, human operators had to manually find the code, review the data, and test the keys. Agentic AI removes the human bottleneck completely.
The speed of these automated attacks is brutal. In one specific case investigated by Microsoft, an AI agent found a leaked secret on GitHub and used it to breach an organization. Within exactly five minutes, the agent moved from finding the key to stealing sensitive data directly from an Azure Key Vault. The AI handled the entire attack chain automatically without hands-on-keyboard interaction. It searched cloud resources, accessed storage accounts, and downloaded files from SharePoint and OneDrive.
The damage spreads quickly across connected systems. Microsoft tracked automated logins starting in October 2026 from specific IP addresses associated with this campaign. In some instances, hackers stole credentials for a vendor-owned multitenant application. This single point of failure allowed the AI agents to access multiple downstream customer environments at once. They even used the compromised accounts to hijack Azure AI and machine learning workloads deployed by the victims. Microsoft also spotted vulnerability exploitation attempts using embedded shell commands.
Key facts
- 5 minutes — Time it took an AI agent to go from finding a GitHub secret to stealing Azure Key Vault data
- ARTEX — The agentic AI offensive framework used by threat actors to scan repositories
- August 2026 — When the malicious AI scanning activity reportedly began
- 199.19.77.84 — IP address used for successful automated service principal sign-ins
Why it matters
The margin of error for developers just dropped to absolute zero. In the past, if you accidentally pushed a hard-coded API key to a public repository, you might have hours or days to realize your mistake. You could delete the commit before a human found it. Now, autonomous agents are constantly watching every public push. If you commit a secret, an AI will find it, parse it, and exploit your infrastructure in minutes. Deleting the commit history does absolutely nothing to save you because the agent has already copied the key and executed the breach.
This changes how startups and enterprise teams must handle authentication. Relying on long-lived client secrets is now a massive liability for any business. If one junior developer makes a copy-paste mistake, an AI agent can pivot through your cloud environment and compromise your customers. Security teams will be forced to abandon static secrets entirely and adopt managed identities. The cost of a single error is no longer just a failed audit. It is a full automated breach executed at machine speed.
For builders
Rotate exposed keys immediately
Deleting a leaked key from your GitHub repository does not invalidate it. You must treat any publicly exposed credential as fully compromised immediately. Revoke and rotate passwords, API keys, and certificates right away to stop attackers from using them against your cloud infrastructure.
Switch to managed identities
Stop storing long-term passwords or secret keys in your source code. Microsoft strongly recommends migrating OAuth applications away from secret-based authentication. Using managed identities eliminates the risk of exposing secrets in your codebase entirely and removes manual secret management.
Enable secret scanning tools
Turn on GitHub Advanced Security or GitHub Secret Protection to automatically scan for credentials in your source code. Use push protection features to block supported secrets before they are ever committed to a repository. This small step protects your environments from automated AI scraping.
My take
I build AI products in public, which means my code is constantly out there. The idea that an autonomous AI agent can find a stray API key and drain a cloud vault in five minutes is terrifying. We can no longer rely on security through obscurity or quick deletes. If you hard-code secrets today, you are just handing the keys to a bot.
Original reporting: Microsoft Security Blog. This is my rewrite and opinion.