A leaked GitHub secret now has a five-minute fuse. Microsoft Threat Intelligence reported on November 5, 2026 that threat actors using the agentic AI framework ARTEX went from scanning public GitHub for exposed secrets to exfiltrating data from an Azure Key Vault in five minutes — and deleting the leaked file afterwards changes nothing, because the credential stays valid until revoked.
This is the sequel to yesterday's post about the 2,539 secrets Claude Code's "Don't Ask Again" setting left on GitHub: that post was about how secrets get out; this one is about what happens next.
What is ARTEX, and how does it hunt leaked secrets?
ARTEX is an open-source agentic penetration-testing framework: you give it a goal, and the AI agent decides how to get there, using ordinary tools like Nmap, curl, and a headless browser. It was published on GitHub in late July 2026 by a user known as "Autumn-27"; its creator pulled the repository on October 8, 2026, after the first reports of threat actors using it.
Pulling it changed nothing. Censys counted roughly 1,400 publicly exposed ARTEX instances across about 800 deployments as of November 4, and a Check Point report published November 5 counted more than 1,800. Copies of the framework are out there, and the management interface doesn't even need to be publicly exposed to be used.
ARTEX is not malware in the classic sense — it ships with only a minimal set of tools, and most of the decision-making is left to the model. The abuse is the story, not a hack of GitHub or Azure. Since August 2026, Microsoft observed threat actors using it to submit large volumes of GitHub queries for secrets, often combining a target organization's name with secret keywords and a cloud or AI service name. Searching public code for credentials is the oldest trick in the book. What changed is the speed: a human used to have to find the repository, read the files, and work out what each key could open. The agent does all three, and then acts on what it finds.
How did one agent go from GitHub to Azure Key Vault in five minutes?
The chain runs like this: the agent finds an OAuth application secret in a public repository, signs in as that application's service principal, requests tokens for Azure Resource Manager, Key Vault, Storage and Microsoft Graph, and pulls data out. In at least one observed case, that whole path — from scanning GitHub to exfiltrating Key Vault data — took five minutes.
The part that should worry every developer is that the agent troubleshoots. Microsoft watched it send a batch of Key Vault requests with the wrong API version, get HTTP 400 errors back, and 28 seconds later retry with the correct version and get HTTP 200 — then do the same with an Azure SQL request 60 seconds after a failure and an Application Insights query 80 seconds after one. That is not a script running a fixed playbook. That is an agent reading an error, fixing its own request, and trying again — at machine speed, with no human in the loop.
Once inside, the agents went after the credentials that unlock more credentials: storage account keys, App Service settings and publishing credentials, connection strings, AI and machine-learning connections, and Azure Kubernetes Service user credentials. They downloaded files from SharePoint and OneDrive, read mailbox items, and searched Microsoft Graph for content of interest. Successful service-principal sign-ins from the campaign's main source IP were observed as early as October 28, 2026, across dozens of applications in multiple tenants — including cases where a multitenant application credential was compromised at the vendor and used to reach downstream tenants.
How big is the pool of secrets waiting to be found?
Enormous — and old. GitGuardian's State of Secrets Sprawl 2026 counted 28.65 million new hardcoded secrets in public GitHub commits in 2025, up 34% on the year before. Four years later, 64% of the valid secrets from 2022 are still active. Leaks of AI-service secrets grew 81% in 2025 alone, and about 5.6% of public repositories contain at least one secret.
That is the hunting ground ARTEX agents search, and AI coding assistants keep adding to it: GitGuardian measured AI-co-authored commits leaking secrets at roughly twice the baseline rate. Yesterday's Claude Code post showed the same pattern up close — 2,539 distinct secrets found in public copies of one settings file.
The damage is already measurable in the field, not just in Microsoft's telemetry. Security firm Todyl, which first spotted the same campaign on November 1, counts 27 organizations reached, 81 files downloaded, and about 2,279 mailbox items accessed. Practitioners on Reddit's r/netsec are treating the whole story mostly as a hygiene story — the tooling is new, the failure is the same one teams have been warned about for years. They're right. The leak is the vulnerability. The agent just removed the delay between the leak and the loss.
The lab test that surprised everyone: ARTEX hunts secrets without a scanner
Here is the insider detail that changed how I think about this. A lab test published November 10 by Security Boulevard ran an ARTEX build (v0.3.15) against a fake GitHub repository with nine planted secrets — and found that the build ships with no secret-scanning code at all. No scanner, no GitHub code, no cloud code. Yet the agent found 8 of the 9 planted credentials anyway, improvising the hunt with plain git and grep.
It started hunting 6 to 13 seconds in — even under a neutral prompt that only asked it to "assess the security posture" and never mentioned secrets. It cloned the repo, walked the full history, listed branches, read the CI workflow, and grepped the working tree. It recovered an AWS key deleted one commit after it was added, found a GitHub token on a side branch, and read an Azure service-principal secret out of the CI workflow. Only 2 of the 9 planted secrets were even present in files at HEAD.
Two caveats, stated honestly because the lab stated them: the model refused to actually use the credentials it found, so the exploitation step is untested — and that refusal belongs to the model provider, not to ARTEX. Point the same framework at an open-weight model with the safeguards stripped out, and the use step may simply happen. The one secret it missed sat in an orphaned commit — still reachable by hash, so a miss, not a safe secret. You cannot block a scanner that was never shipped. You can rotate the secret it would otherwise find.
Who else is running ARTEX?
The five-minute case is one campaign among several, and the trend runs from espionage toward plain financial crime — and Microsoft does not attribute it to any of the groups below:
- Storm-3358 (financial crime): Microsoft reported on November 6 that this Cambodia-based, financially motivated group began using ARTEX against financial organizations in October 2026, mainly in Southeast Asia. It scans internet-facing systems, exploits flaws like anonymous file upload and server-side request forgery, and installs remote access trojans (WISP, vshell, AdaptixC2) for persistence.
- Storm-0940 (espionage): Microsoft's October 21 report ties this China-state-aligned actor to ARTEX-driven attacks against hundreds of organizations globally, including the ConnectWise Cloud Backup supply-chain compromise. It attempted sign-ins to more than 2,250 tenants, and in multiple instances went from initial targeting to privileged cloud access in under three hours.
What to do today: four fixes that actually close the leak
1. Treat every public secret as compromised. Scan your public GitHub presence — your repositories, history, branches and forks, and your developers' personal repositories, where most corporate leaks actually happen — and revoke or rotate anything you find before you investigate whether it was used. Deleting the file or rewriting history does not invalidate the credential.
2. Stop storing long-lived secrets. Move Azure workloads to managed identities — credentials stay out of code entirely. For GitHub Actions, use OpenID Connect instead of a stored Azure client secret. Every secret you stop storing is a secret no agent can find.
3. Block the push. Turn on GitHub secret scanning with push protection, so supported secrets are blocked before they reach the repository, and add pre-commit scanning so a secret is never committed in the first place. The cheapest secret to rotate is the one that was never pushed.
4. Hunt for the signs. In your Entra sign-in logs, look for the campaign's main source IP, 199.19.77.84, and for sign-in errors AADSTS7000215 (invalid secret) or AADSTS7000222 (expired secret) — either means someone holds a credential for your app, and a failure followed by a success is urgent. Look for behaviour, not just the IP: one address signing in as three or more service principals, or one app requesting tokens across Azure Resource Manager, Key Vault, Storage and Graph in a short window. Microsoft's own recommendation is to block 199.19.77.84 as a named location in a Conditional Access policy aimed at workload identities.
What we'd do
At Lynxwell Digital, this is the first thing we check when an AI-built app lands on our desk for rescue: where are its secrets, and are any already public? AI-built apps are the highest-risk source of leaked credentials we see — developers building fast with Lovable, v0, or Claude Code ship .env files and API keys into public repos without ever meaning to, and our Lovable production checklist exists because we've watched it happen. What we tell clients is simple: assume a secret is already out there, rotate first and ask questions later, and move the app to managed identities or OIDC so the next leak finds nothing. If you want us to do that check for you, our Launch Safety Audit is $390 — free if we find nothing critical. Or start with a free rescue audit and we'll tell you what we'd fix first.
FAQ
What is ARTEX?
ARTEX is an open-source agentic penetration-testing framework that uses an AI model to run offensive security tasks autonomously. It was published on GitHub in late July 2026 and pulled by its creator on October 8, 2026, after threat actors began using it.
How fast can a leaked GitHub secret be abused?
In one case Microsoft observed, an AI agent went from scanning GitHub for a leaked secret to exfiltrating data from an Azure Key Vault in five minutes. The searches had been running since August 2026; successful sign-ins were observed from October 28, 2026.
Does deleting a leaked secret from GitHub make it safe?
No. A publicly exposed credential stays usable until someone revokes or rotates it. Deleting the file, the commit, or rewriting git history does not invalidate it. In a lab test, an ARTEX build recovered an AWS key deleted one commit after it was added — git history keeps the secret alive.
How do I check if my secrets are exposed on GitHub?
Scan your public repositories — including git history, branches, and forks — plus your developers' personal repositories. GitHub's secret scanning and public monitoring cover exposure beyond the repositories you own. Assume anything found is compromised: revoke or rotate it first, then investigate whether it was used.
What is the fastest fix for a leaked Azure credential?
Revoke or rotate it immediately, then move the workload to a managed identity or OpenID Connect so no long-lived secret is left to leak. Deleting the leaked file is not a fix. If you see sign-in errors AADSTS7000215 or AADSTS7000222 for your app, someone already holds one of its credentials.
If your app was built fast — with Lovable, v0, Claude Code, or Cursor — assume a secret is sitting in a public repo somewhere. Send us your repo URL and we'll run the Launch Safety Audit: find the leaked secrets, rotate what needs rotating, and move you to credentials that can't leak. It's the same AI engineering work we do for every AI-built app we rescue.