26,400 working cloud and AI credentials found in public Gitee repositories
A researcher scanned 7.25 million public repositories on Gitee, China's largest Git platform, and found 26,400 unique credentials that still worked, led by Alibaba Cloud access keys. One was an active organization-admin credential for a major enterprise AI platform.
Independent researcher Ben Zimmermann scanned 7,256,531 public repositories on Gitee, China's largest Git hosting platform, and found 26,400 unique credentials that still worked when tested, he wrote on MongoDB's engineering blog on October 28. He ran two secret scanners, TruffleHog and Kingfisher, over each repository's full commit history and kept only credentials the issuing service accepted. Alibaba Cloud access keys were the largest group, and AI provider keys from DeepSeek, OpenAI and Zhipu followed in the thousands. One finding was "an active organization-admin credential for a major enterprise AI platform." The scanners overlapped on only 1,001 credentials, so either tool alone would have caught about half; Kingfisher found all 1,489 Zhipu keys, which TruffleHog has no detector for. Zimmermann sent the most exposed vendors their lists but did not contact individual developers.
Why it matters
The scan read commit history, so a key a developer later deleted from the code still counted. Deleting a secret is not revoking it, the same lesson as LiteLLM's admin key, which was removed from a public repository within hours and still worked months later. A live AI provider key in a public repository is a direct line to someone else's bill, which is what LLMjacking runs on.
If a key ever reached a public repository on any platform, revoke it at the provider and issue a new one; rewriting history does not help. Run more than one scanner, since detector coverage differs by vendor, and restrict cloud keys to the APIs they need. The technique page is secrets in repositories and CI, and our secrets management guide covers replacing long-lived keys with short-lived credentials.
Source: MongoDB Engineering Blog
Related on Start with Identity
- BlogGoogle: LLMjacking starts with stolen cloud identities and has cost some companies $1 million
Google Threat Intelligence Group and Mandiant say LLMjacking intrusions ran up more than $100,000 in fraudulent AI charges in a day and $1 million in total at s
- BlogIBM makes Agent Identity and HashiCorp Vault 2.2 generally available to govern AI agents
At TechXchange 2026 on October 27, IBM made Agent Identity and HashiCorp Vault 2.2 generally available. Agent Identity records each AI agent's owner, lifecycle
- BlogInfisical raises a $40 million Series B to build secrets and credential access for AI agents
Infisical announced a $40 million Series B on October 27 at a $600 million valuation, led by Elad Gil. The open-source secrets company says it will invest in se
- CVEtj-actions/changed-files tags repointed to dump CI secrets into logs
An attacker repointed tj-actions/changed-files version tags to a commit that read the GitHub Actions runner's memory and printed its secrets into workflow logs.
- CVECommvault Web Server zero-day that exposed Metallic Microsoft 365 app secrets
An authenticated webshell flaw in Commvault Web Server, used as a zero-day in Commvault's Azure environment, where the actor may have reached client secrets cus
- ReportIdentity Breach Report 2026: how attackers get in
120 identity breaches, 2021 to 2026: MFA was bypassed in 25 of the 40 with a known MFA status, and 45.8% of 2025-2026 cases had no login for MFA to protect.