What did the Gitee secrets research find?
In research published on MongoDB's Builder Blog, independent researcher Ben Zimmermann, working with MongoDB's Kingfisher team, enumerated 7,256,531 public repositories on Gitee and scanned them with TruffleHog and Kingfisher in verified-only modes. The scans found 26,400 unique credentials that were live at scan time, about 3.64 per 1,000 repositories.
The largest groups were Alibaba Cloud keys (9,473), YouTube API keys (3,805) and DeepSeek keys (3,170), with Kingfisher also finding 1,489 Zhipu and 1,198 OpenAI keys. The findings included an active organization-admin credential for a major enterprise AI platform. The researcher reported the credentials to the highest-volume vendors. This is a research finding, not a breach of Gitee, and live at scan time doesn't mean a key was abused.
Which credentials were found?
- Alibaba Cloud access keys: 9,473.
- YouTube API keys: 3,805.
- DeepSeek keys: 3,170. Kingfisher also found 1,489 Zhipu and 1,198 OpenAI keys.
- An active organization-admin credential for a major enterprise AI platform.
How to check if you're affected
- Scan your repositories, and any mirrors you keep on Gitee or other public hosts, for hardcoded credentials. The research found that TruffleHog and Kingfisher together caught more than either alone.
- Check whether each finding is still live with its provider, so you fix working keys first.
- Search full git history, not just the latest commit, because a deleted secret stays in history.
What to do now
- Revoke exposed credentials at the vendor. The research treats vendor-side revocation as more reliable than waiting for the person who leaked the key.
- Move secrets into a secrets manager and inject them at runtime.
- Add pre-commit and pull request checks so new secrets don't reach public repositories.
Why live-key verification matters
A scan of millions of repositories returns far more matches than anyone can rotate in a day. Checking which credentials still authenticate turns that list into a short queue of keys that can actually be abused right now. The Gitee numbers also show how AI provider keys now sit alongside cloud keys at the top of what gets leaked, which matches the AI key theft seen across platform breaches in October 2026.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify finds credentials in code and verifies which ones still work with the provider that issued them (AWS, GCP, Azure, GitHub, GitLab, Stripe and Slack), so live keys rank first, then routes rotation to each owner. Rotation happens with the provider; Nullify doesn't rotate keys.
These are secrets committed to code, which is exactly where a live-key check applies.
Frequently Asked Questions
How many live secrets were found on Gitee?
The research found 26,400 unique credentials that were live at scan time across 7,256,531 public Gitee repositories, about 3.64 per 1,000 repositories. Alibaba Cloud, YouTube and DeepSeek keys were the largest groups.
Was Gitee breached?
No. This was a research scan of public repositories for credentials that developers committed. Gitee's platform wasn't compromised, and a key being live at scan time doesn't mean it was abused.
How do I find leaked secrets in my own repositories?
Scan code and full git history with secret scanners, verify which findings are still live with their providers, revoke live keys at the issuer, and add pre-commit and pull request checks so new secrets don't get committed.
Update Log
- Nov 17, 2026: page published from the October 28 research post.