How Did a GitHub Action Compromise Impact Thousands of Repositories?

Article Highlights
Off On

A significant security incident has rocked the software development community, specifically targeting GitHub Actions. This breach, identified as CVE-2025-30066, was a supply chain attack affecting over 23,000 code repositories. At its core, this attack involved the GitHub Action known as tj-actions/changed-files, which enabled attackers to leak critical secrets like passwords from public repositories. The incident underscores the vulnerability of public repositories in the software supply chain and the importance of rigorous security practices.

The Attack Unveiled

The compromise began with malicious actors introducing a harmful commit into the popular tj-actions/changed-files GitHub Action. This commit contained a Node.js function with base64-encoded instructions that downloaded a malicious Python script. The script’s purpose was to scan the GitHub Runner’s memory, hunting for sensitive information such as passwords and other credentials crucial for CI/CD processes.

These secrets, found in GitHub Runner’s memory, were subsequently printed in the build logs of the compromised Action. Because these logs were publicly accessible, anyone with the right access could retrieve the exposed information. Varun Sharma of StepSecurity emphasized the ease with which these exposed secrets could be exploited if the logs were public. The ability to expose vital credentials made the attack particularly dangerous, affecting numerous public repositories and highlighting the significant flaw in the system’s design.

Discovering the Compromise

StepSecurity played a pivotal role in detecting the breach, tracing the malicious activity back to mid-March. Cybersecurity firm Sysdig supported these findings, unraveling how the Node.js function decoded the payload to fetch additional Python code from a GitHub gist. This code mapped the GitHub Runner’s memory, used regular expressions to search for credentials, and logged the extracted secrets. GitHub’s prompt response involved deactivating the compromised Action to prevent further data leaks.

The token allowed privileged access to targeted repositories, prompting repository maintainers to revoke the PAT, update the bot’s password, restrict permissions, and enforce passkey requirements. This chain of events highlighted the importance of securing personal access tokens, as their compromise can lead to extensive operational disruptions and sensitive data exposure.

Broad Impact on Repositories

Researchers from Wiz pointed out that the primary threat affected public repositories due to the accessibility of logs and secrets. Numerous repositories, including those of large organizations, had secrets such as AWS access keys and GitHub Personal Access Tokens compromised. This highlighted the wide-reaching impact and the vulnerability of public repositories to such attacks. The exposure of these credentials posed a significant risk since they could be used to gain unauthorized access to additional systems and data.

Dimitri Stiliadis from Endor Labs speculated that the attackers had broader motives than just accessing secrets. He suggested that the ultimate goal might have been to compromise the software supply chain for other open-source libraries and artifacts, posing a potential risk to thousands of packages involved in public repository CI pipelines. This aspect of the attack emphasizes the interconnected nature of software development repositories and the cascading effects a single compromise can have on the broader ecosystem.

Strengthening Security Measures

A significant security incident has sent shockwaves through the software development community, specifically targeting GitHub Actions. This breach, cataloged as CVE-2025-30066, was a supply chain attack impacting more than 23,000 code repositories. At the heart of this attack was the GitHub Action known as tj-actions/changed-files. This vulnerability allowed attackers to seamlessly leak critical secrets such as passwords from public repositories. This incident highlights the vulnerabilities public repositories face in the software supply chain and emphasizes the necessity of stringent security protocols.

The breach’s extent reveals that even widely trusted tools can harbor flaws, pointing to the growing need for developers and organizations to prioritize security at every level from development to deployment. Ensuring that security parameters are strictly enforced can help mitigate such risks. The software development community must take this incident as a wake-up call and adopt more rigorous measures to protect against similar threats in the future.

Explore more

Unlock Success with the Right CRM Model for Your Business

In today’s fast-paced business landscape, maintaining a loyal customer base is more challenging than ever, with countless tools and platforms vying for attention behind the scenes in marketing, sales, and customer service. Delivering consistent, personalized care to every client can feel like an uphill battle when juggling multiple systems and data points. This is where customer relationship management (CRM) steps

7 Steps to Smarter Email Marketing and Tech Stack Success

In a digital landscape where billions of emails flood inboxes daily, standing out is no small feat, and despite the rise of social media and instant messaging, email remains a powerhouse, delivering an average ROI of $42 for every dollar spent, according to recent industry studies. Yet, countless brands struggle to capture attention, with open rates stagnating and conversions slipping.

Why Is Employee Retention Key to Boosting Productivity?

In today’s cutthroat business landscape, a staggering reality looms over companies across the United States: losing an employee costs far more than just a vacant desk, and with turnover rates draining resources and a tightening labor market showing no signs of relief, businesses are grappling with an unseen crisis that threatens their bottom line. The hidden cost of replacing talent—often

How to Hire Your First Employee for Business Growth

Hiring the first employee represents a monumental shift for any small business owner, marking a transition from solo operations to building a team. Picture a solopreneur juggling endless tasks—client calls, invoicing, marketing, and product delivery—all while watching opportunities slip through the cracks due to a sheer lack of time. This scenario is all too common, with many entrepreneurs stretching themselves

Is Corporate Espionage the New HR Tech Battleground?

What happens when the very tools designed to simplify work turn into battlegrounds for corporate betrayal? In a stunning clash between two HR tech powerhouses, Rippling and Deel, a lawsuit alleging corporate espionage has unveiled a shadowy side of the industry. With accusations of data theft and employee poaching flying, this conflict has gripped the tech world, raising questions about