ARTEX: abusing public secrets on GitHub

GitHub, Azure

Attackers using ARTEX to hunt exposed secrets on public GitHub and move into Azure tenants

Do this now

Rotate any secrets exposed on public GitHub and check Azure tenants for unauthorized access.

Who should check: teams running Azure / M365

First seen: 6 Nov 2026
Last update: 6 Nov 2026, 21:17 UTC
Source: news
On the menu as: Azure / M365

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## ARTEX: abusing public secrets on GitHub
Severity: unknown. Patch status: fix status unknown.
Affected: GitHub, Azure

Attackers using ARTEX to hunt exposed secrets on public GitHub and move into Azure tenants

## Steps
1. This incident involves a provider (azure). Search config, CI and env templates (.env.example, wrangler.toml, vercel.json, terraform, workflow secrets) for credentials stored there. List each secret by name, where it is used, and how to rotate it. Never print secret values.
2. No source names a fix yet; check the vendor advisory. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://blog.gitguardian.com/the-agents-have-now-found-your-secrets-on-github-artex-is-abusing-public-secrets-right-now/
https://pwned.coffee/i/artex-abusing-public-secrets-on-github

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 7 Nov 2026, 18:18 UTC

Sources: KEV – CVE record – Vendor –

Sources

blog.gitguardian.com: The Agents Have Now Found Your Secrets On GitHub: ARTEX Is Abusing Public Secrets Right Now

Follow on X

Totalone coffee