INSPECTING ARCHIVED INTELLIGENCE (OUTDATED VERSION).
Gitee Repositories Expose 26,400 Valid Cloud and AI Credentials
|
2026-10-29 11:33
HIGH
LOW
DATA BREACH
Executive Summary
AI-generated
On October 28, an independent researcher discovered that approximately 26,400 valid cloud and AI credentials were exposed in public Gitee repositories. The identified entity behind the incident is Ben Zimmermann, a researcher who scanned over 7.25 million public Gitee repositories to find these credentials. These affected entities include developers from various countries, with the majority of keys belonging to Alibaba Cloud users, followed by YouTube API key holders and OpenAI account owners. The attack works by scanning each repository's full commit history using secret scanners TruffleHog and Kingfisher, which then try each credential against its respective service. As a result, many developers who left their credentials in public code on Gitee may have inadvertently exposed sensitive information that could be used without consent.
Technical Mitigations AI-generated
• Reset credentials and API keys that may have been exposed, and review access logs for the affected accounts or integrations.
Intelligence Metadata
Actors / Malware / CVEs / Campaigns
Target & Sectors
NORTH_AMERICA
NORTH_AMERICA
Incident Timeline
October 28
An independent researcher discovered 26,400 valid cloud and AI credentials exposed in public Gitee repositories by scanning 7.25 million of them on October 28.
Click on any entity below to view its context and source!
organisation
Independent
Independent researcher
Ben Zimmermann
found them by scanning 7.25 million public Gitee repositories and
reported the results
on October 28.
general_metric
7.25 Gitee repositories
Independent researcher
Ben Zimmermann
found them by scanning 7.25 million public Gitee repositories and
reported the results
on October 28.
the late 2000s
Threat actors used outdated cloud and AI credentials stored in public Gitee repositories dating back to the late 2000s.
2026/10/29
TruffleHog found 12,737 valid cloud and AI credentials in public Gitee repositories.
Click on any entity below to view its context and source!
organisation
Ministry of Industry and Information Technology
Gitee and Other Code Hosts
China's Ministry of Industry and Information Technology
chose Gitee in 2020
as the base for a national open-source code-hosting platform.
organisation
Gitee
26,400 credentials that developers left in public code on
Gitee
, a Chinese code-hosting service, still worked when a researcher tested them.
data_breach
26,400 credentials
26,400 credentials that developers left in public code on
Gitee
, a Chinese code-hosting service, still worked when a researcher tested them.
organisation
AccessKey
Most were keys for cloud and AI services, led by 9,473 Alibaba Cloud AccessKey pairs.
organisation
BigModel AI
What Was Exposed
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.
organisation
GitHub
Smaller numbers were found for GitHub, AWS, Google Cloud and Google's Gemini.
organisation
AWS
Smaller numbers were found for GitHub, AWS, Google Cloud and Google's Gemini.
organisation
Google
Smaller numbers were found for GitHub, AWS, Google Cloud and Google's Gemini.
organisation
API
That can cause "data loss, unexpected charges," a used-up monthly quota, and interrupted API access.
organisation
TruffleHog
Deleting a key from the code or rewriting the repository's history
does not revoke it
, as noted by TruffleHog's maker, Truffle Security.
organisation
Truffle Security
Deleting a key from the code or rewriting the repository's history
does not revoke it
, as noted by TruffleHog's maker, Truffle Security.
organisation
ActionTrail
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.
organisation
OSS
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.
organisation
SLS
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.
organisation
OpenAI
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.
organisation
Zimmermann
Two Scanners, Different Results
MongoDB makes Kingfisher, and Zimmermann's post was developed with its Kingfisher team.
organisation
Teams
Teams that rely on a single scanner should verify its detectors against the services they use.
organisation
Gitee's
Gitee's public API is limited, and a
2021 attempt
to study leaked credentials on the site gave up because of it.
organisation
GitLab
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).
data_breach
3.64 working credentials
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).
data_breach
2.39 Bitbucket
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).
data_breach
12,737 credentials
In this scan, TruffleHog found 12,737 credentials that worked, and Kingfisher found 14,664, but only 1,001 were found by both.
Tactical Metrics
Metrics
data_breach
26,400
Credentials
Click for context!
26,400 credentials that developers left in public code on
Gitee
, a Chinese code-hosting service, still worked when a researcher tested them.
Metrics
data_breach
4
Working Credentials
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).
Metrics
data_breach
2
Bitbucket
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).
Metrics
data_breach
12,737
Credentials
In this scan, TruffleHog found 12,737 credentials that worked, and Kingfisher found 14,664, but only 1,001 were found by both.
Intelligence Sources
The Hacker News
2026-10-29
Unpublish from Social Media?
Are you sure you want to delete this podcast video from all synchronized social networks (YouTube, Facebook, Threads)?
Important:
Due to Meta API restrictions, Instagram Reels cannot be deleted automatically via API by third-party apps.
View Profile to Delete Manually
View Profile to Delete Manually
Tactical Intelligence
Report Intelligence Issue
Podcast Options
Generate
Incident Version History
CURRENT VERSION
Last Updated: 2026-10-30T12:12
Comprehensive Tactical Telemetry
Highly Correlated Entities
19x
organisation
Identified Entity
Ministry of Industry and Information Technology
entity
6x
timeline
Temporal Reference
2020
date
2x
target region
Target Country
China
country
2x
tactic
MITRE ATT&CK Technique
T1589.001 - Credentials
technique
2x
data breach
Credentials
26,400
credentials
2x
general metric
Kingfisher
14,664
kingfisher
Contextual Telemetry
Context Block
13 METRICS
general metric
Valid Cloud
26,400
valid cloud
general metric
Gitee Repositories
7,250,000
gitee repositories
general metric
Accesskey Pairs
9,473
accesskey pairs
general metric
Date
12,242
date
general metric
Api Keys
3,805
api keys
general metric
Deepseek Keys
3,170
deepseek keys
general metric
Keys
1,489
keys
general metric
Openai Keys
1,348
openai keys
data breach
Working Credentials
4
working credentials
general metric
Repositories
1,000
repositories
general metric
Gitlab
3
gitlab
data breach
Bitbucket
2
bitbucket
general metric
Rate
2
rate
Click on any entity below to view its context in the main text!
Selective Unpublish
Select the networks you want to remove this post from. The system will try to delete the real post through the API and clean the database so you can publish it again.
By navigating this website, you accept the use of strictly necessary technical cookies for session security and basic platform functionality. We do not use tracking or advertising cookies. Read our Privacy Policy.