The GitHub account hijacking campaign exposed CI/CD environments to credential theft, demonstrating how compromised developer accounts can put repository secrets and cloud credentials at risk.
Attackers used credentials from 4,837 GitHub accounts to target 61,764 repositories, with malicious payload execution confirmed in at least 1,806.
Organizations should investigate affected accounts and workflows, rotate potentially exposed CI secrets, review cloud roles, and restrict excessive repository permissions.
Hexnode’s MFA, Conditional Access, and device-compliance-based controls can strengthen developer account security, while repository investigation and credential remediation require separate action.
A large-scale credential theft campaign has exposed the risks of compromised developer accounts in enterprise CI/CD environments. Starting November 10, an attacker used stolen credentials from 4,837 GitHub accounts to distribute a secret-stealing payload across repositories accessible to those accounts.
The GitHub accounts hijacked CI secret stealer campaign involved probe pull requests across 61,764 repositories, with the malicious payload confirmed to have executed in at least 1,806. The incident highlights how compromised repository access can extend beyond source code, potentially exposing sensitive workflow secrets and cloud credentials.
What happened in the GitHub account hijacking campaign?
Beginning Tuesday, November 10, the attacker leveraged stolen GitHub credentials to access repositories where the compromised accounts held write permissions.
Rather than targeting individual repositories in isolation, the campaign used those existing permissions to distribute a secret stealer across a much larger collection of projects.
The attacker opened probe pull requests in 61,764 repositories. The payload subsequently executed in at least 1,806 repositories, creating potential exposure for the secrets and cloud roles accessible to those workflows.
The compromised accounts also overlapped with accounts affected by an earlier October campaign known as GhostAction. This connection indicates that previously stolen credentials remained relevant to the latest activity, although the available information does not establish whether the same attacker conducted both campaigns.
Researchers assessed that the campaign primarily targeted CI workflow secrets and cloud credentials. However, malicious code also reached certain software packages and modules, introducing additional downstream security risks.
Featured Resource
Cybersecurity kit
Access essential cybersecurity resources to strengthen security, reduce risk, and improve cyber resilience.
How did the GitHub accounts hijacked CI secret stealer campaign work?
The campaign exploited the relationship between repository write permissions and the credentials available within CI workflows.
Using compromised GitHub accounts, the attacker introduced a secret-stealing payload into repositories those accounts could modify. Probe pull requests formed part of the activity, allowing the attacker to target repositories at considerable scale.
The critical exposure occurred when the malicious payload executed within a CI workflow.
Such workflows can access secrets and cloud roles needed to perform authorized operations. When malicious code runs in that environment, those credentials may become accessible to the attacker.
As a precaution, organizations should treat every secret and cloud role accessible to a workflow in which the stealer executed as potentially compromised and rotate or revoke the affected credentials. Confirmed payload execution does not independently establish that every accessible credential was successfully exfiltrated.
However, the available details do not establish the precise execution mechanism, the individual credentials successfully extracted, or the complete extent of subsequent unauthorized access.
This distinction matters when assessing exposure. Confirmed payload execution establishes the need for credential remediation, but it does not independently establish that every exposed credential was subsequently used.
Why does this campaign matter for enterprise security?
The GitHub accounts hijacked CI secret stealer campaign demonstrates how compromised developer identities can create risks beyond the repositories they directly access.
A single account with repository write permissions may provide an attacker with access to CI workflows containing sensitive credentials. Consequently, the impact of account compromise depends not only on repository permissions but also on the secrets and cloud roles available to those workflows.
For enterprise IT and security teams, this creates two immediate priorities: identifying potentially affected accounts and determining which credentials require rotation.
Organizations must also review the access granted to developer and service accounts, particularly where those identities can modify repositories connected to CI/CD pipelines.
Without understanding these dependencies, teams may address the compromised GitHub account while leaving exposed workflow credentials active.
How can Hexnode help strengthen developer identity security?
Compromised developer accounts highlight the importance of securing access to enterprise applications and maintaining appropriate authentication controls.
Hexnode IdP supports multi-factor authentication (MFA), Conditional Access policies, and user or group assignments for applications configured with the identity provider. These capabilities can help organizations strengthen authentication and manage access to supported enterprise applications used by development teams.
Hexnode UEM can also complement identity security through its integration with Microsoft Entra Conditional Access. For supported Android, iOS/iPadOS, and macOS devices, Hexnode UEM shares device compliance information that Microsoft Entra ID can use when evaluating configured access policies.
However, these capabilities do not establish direct protection for GitHub personal access tokens, GitHub Actions secrets, or cloud service credentials.
Organizations responding to the campaign should investigate compromised GitHub accounts, revoke affected access credentials, rotate potentially exposed CI/CD secrets, review repository permissions, and examine cloud identity configurations for unauthorized changes.
Hexnode’s documented capabilities can complement broader identity security practices, but they do not independently detect malicious GitHub workflows, identify stolen CI secrets, or remediate compromised GitHub accounts.
FAQs
How can stolen GitHub credentials expose CI/CD pipeline secrets?
Attackers can use compromised GitHub accounts with repository write permissions to introduce malicious code into accessible projects. If that code executes within a CI workflow, it may access secrets, authentication tokens, and cloud credentials available to the workflow.
Does opening a malicious pull request automatically expose GitHub Actions secrets?
No. Opening a pull request does not automatically grant its code access to CI secrets. Exposure depends on the workflow’s execution conditions, permissions, and available credentials, making confirmed payload execution a critical investigation checkpoint.
What should organizations do if a GitHub Actions workflow executed the secret stealer?
Organizations should treat secrets and cloud roles accessible to the affected workflow as potentially compromised. Security teams should rotate exposed credentials, review workflow permissions, investigate unauthorized activity, and verify that malicious code has been removed.
Strengthening identity security across CI/CD environments
This campaign reinforces the importance of treating developer and service account credentials as critical enterprise security assets.
With malicious payload execution confirmed across at least 1,806 repositories, affected organizations should prioritize credential rotation, repository access reviews, and assessment of exposed cloud roles.
Identity-aware access policies and MFA can help reduce future exposure, but they must complement direct investigation and remediation of affected workflows.
The practical takeaway is clear: securing developer identities also means understanding the credentials and permissions accessible through their CI/CD environments.
Strengthen Developer Endpoint Security
Protect developer endpoints, detect credential theft, and strengthen cloud security with Hexnode.
Content writer at Hexnode. Fueled by good coffee and the occasional cat cuddle, I enjoy crafting content that informs, connects, and resonates. Nothing excites me more than knowing my words have been read, appreciated, and maybe even bookmarked.