26,400 Valid Cloud and AI Credentials Found Exposed in Public Gitee Repositories Swati KhandelwalOct 29, 2026Cloud Security / Artificial Intelligence 26,400 credentials that developers left in public code on Gitee, a Chinese code-hosting service, still worked when a researcher tested them. Anyone who copied one from that code could have used it. Independent researcher Ben Zimmermann found them by scanning 7.25 million public Gitee repositories and reported the results on October 28. Most were keys for cloud and AI services, led by 9,473 Alibaba Cloud AccessKey pairs. Zimmermann sent the vendors with the most exposed keys a list of their credentials, but he did not contact the developers who leaked them. When he published, he had not confirmed that any of the reported credentials had been revoked. So anyone who has pushed a key to a public Gitee repository cannot assume it has been revoked. The scan ran for about a month, but Zimmermann did not provide the dates, so it is unclear how long ago the credentials were tested. He also did not say whether anyone else had used them. He ran two secret scanners, TruffleHog and Kingfisher, over every repository. Both tried each credential against the service that issued it and kept only those that worked, he wrote. The scanners read each repository's full commit history. A key that a developer later removed from the code could still be found and counted there. The 26,400 figure counts each credential once, regardless of how many repositories it appeared in. By commit date, 12,242 of the credentials came from 2025, nearly half the total. Some dated to the late 2000s. After the Alibaba Cloud keys, the largest groups were 3,805 YouTube API keys, 3,170 DeepSeek keys, 1,489 keys for Zhipu's BigModel AI platform, and 1,348 OpenAI keys. Smaller numbers were found for GitHub, AWS, Google Cloud and Google's Gemini. One of the credentials was "an active organization-admin credential for a major enterprise AI platform," Zimmermann wrote. He did not name the platform or say what the credential could reach. What a working key lets someone do depends on the service. OpenAI says that a compromised key allows another person to use the account's quota without the owner's consent. That can cause "data loss, unexpected charges," a used-up monthly quota, and interrupted API access. A YouTube API key is a Google Cloud API key that identifies a project, Google says. Without API restrictions, such a key can be used with every API that accepts Google Cloud keys. Treat any key that has ever been in a public Gitee repository as exposed, and revoke it at the provider. Deleting a key from the code or rewriting the repository's history does not revoke it, as noted by TruffleHog's maker, Truffle Security. Alibaba Cloud: create a new AccessKey pair, switch your apps to it, then disable and delete the old pair. Check for unexpected charges and for resources created or deleted that you did not need, Alibaba Cloud's leak response plan says. ActionTrail shows the key's API calls for the last 90 days, but data operations in services such as OSS and SLS have to be checked in each service's own logs. Google and YouTube API keys: rotate the key, which creates a new key with the same restrictions, update your apps to use it, then delete the old key. Add API restrictions so the key works only with the APIs you need. OpenAI: rotate the key immediately from the API Keys page, as OpenAI advises, and set spend limits to help limit charges from a leaked key. MongoDB makes Kingfisher, and Zimmermann's post was developed with its Kingfisher team. In this scan, TruffleHog found 12,737 credentials that worked, and Kingfisher found 14,664, but only 1,001 were found by both. Each tool alone found about half of the total. TruffleHog found almost all of the Alibaba Cloud keys. Kingfisher found all 1,489 BigModel keys, because TruffleHog has no detector for Zhipu's keys, Zimmermann wrote. Teams that rely on a single scanner should verify its detectors against the services they use. China's Ministry of Industry and Information Technology chose Gitee in 2020 as the base for a national open-source code-hosting platform. Gitee's public API is limited, and a 2021 attempt to study leaked credentials on the site gave up because of it. Gitee's rate, 3.64 working credentials per 1,000 repositories scanned, is higher than the rates from earlier scans of GitLab (3.11) and Bitbucket (2.39). Those scans used only TruffleHog, Zimmermann wrote. Based on TruffleHog's results alone, Gitee's rate is 1.76, but that count excludes services TruffleHog does not cover, such as Zhipu. So neither figure shows which platform leaks more. Found this article interesting? Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post. API Security, artificial intelligence, Cloud security, Data Exposure, Supply Chain ⚡ Weekly Recap: 98 Zero-Days, Rogue AI Agents, $100M Crypto Theft, 700 Supermarkets Hit and More Eight eMudhra CA Keys Compromised, Triggering Emergency Fixes Across Browsers and Software Generative AI Is Erasing Behavioral Tells, Weakening Behavior-Only Detection, Proofpoint Reports Hackers Hijack Five OVHcloud CLI Releases to Distribute Secret-Stealing Malware Critical FortiSIEM Flaw Gets Public Exploit PoC for Unauthenticated Remote Code Execution Hackers Use Autonomous AI Agents to Breach Company Websites, Target Over 1,200 Sites State Bank of India Confirms Data Leak After 3,897 Customer Records Found on Dark Web Unpatched Broadcom Wi-Fi Flaw Lets Attackers in Range Run Code as Root on Routers Researchers Demonstrate Node2Shell RCE Exploit on Node.js Build Using Crafted Brotli Data Attackers Hijacked Over 300 Tor Exit Relays to Intercept SSH Connections Go Issues Emergency Update Blocking Eight CA Keys Over Undisclosed Security Concerns PHP Warns of Another Unpatched RCE Risk Two Days After Emergency PHP2Shell Patches WhatsApp Hid Instructions in Help Pages Telling Its AI Chatbot Not to Recommend Privacy Regulators PHP2Shell: Two Unpatched Critical PHP RCE Flaws (CVSS 9.2) Trigger Emergency Security Alert Hackers Exploit Plex2Shell Flaws to Install Crypto Miners and Linux Proxy Backdoor Ruby Fixes Three Regex Engine Bugs Responsible for Four Critical GitLab RCE Flaws ThreatsDay: AI Secrets Leak, PingCAP Source Theft, Signal Hang-Up Flaw, Laravel Auth Bypass + 21 More Two CVSS 9.0 Linux KSMBD RCE Flaws Disclosed on Public Mailing Lists Before Kernel Fixes Critical Flaw in Python’s Popular Pillow Image Library Allows Code Execution via a Crafted Image Critical GitLab Flaw (CVSS 10.0) Could Allow Unauthenticated RCE Across 12 Years of Releases New QPACK Flaws Can Crash HTTP/3 Servers, Trigger Up to 4,000-Fold Memory Amplification OpenCode Console Breach May Have Exposed OpenAI, Anthropic, and Google API Keys PHP Issues Emergency Patches for Two Critical PHP2Shell RCE Flaws as Exploit Attempts Emerge Brotli Decoder Flaw Behind Node.js RCE Also Affects Bun, Python and Other Widely Used Software No Exploit Yet? Preview the Summit Demo on Validating CVE Exposure Download the 2026 Agent Security Report for a Five-Step Risk Reduction Framework Get the Five-Stage Identity Maturity Roadmap for Governing AI Agents Benchmark Your AI Risk Priorities Against 1,600 CISOs—Download the 2026 Report Your SOC Has an Identity Blind Spot. Here's How to Fix It Learn how to close critical identity visibility gaps in your SOC, detect hidden threats, and accelerate incident response across human, machine, and AI identities. Join the Session Roadmap for AI-Ready Security Operations Evaluate Attack Surface Visibility With an AI Threat Readiness Framework Learn how to assess AI threat readiness, strengthen attack surface visibility, and prepare security operations for emerging threats in this practical webinar. 11 Real Stories: How Identity Exposure Unlocks Active Attack Paths Map cross-domain privilege escalation to sever breach routes at key choke points. The 2026 Identity Crisis: Why Your IAM is Only Half the Story Stop driving blind. See the identity blind spots traditional IAM misses. Watch now. FBI Cyber Division's Brett Leatherman Keynotes SANS CDI 2026, Dec 15 Join SANS CEO James Lyne and the FBI on ransomware disruption and intel sharing, during SANS training in D.C. Governance Sets the Ceiling on Your AI Security Program See the five moves that raise a Stage 2 Govern score to a defensible Stage 3. Your Backup Isn't Ransomware-Proof Just Because It Exists Why Root and Jailbreak Detection Alone Cannot Guarantee Mobile App Security The Least Trusted Author Sets the AI Agent's Privilege Security Rests on Hard Math Problems. Quantum and AI Are Both Coming for Them