Skip to main content
Mallory
← Back to News
build-pipeline-compromiseleaked-secret-api-keyvendor-distribution-compromisewidely-deployed-product-advisory

Compromise of tj-actions/changed-files Exposed CI Secrets in GitHub Actions

Supply Chain Risk · 4 sources · Updated 4mo ago · First seen Mar 26, 2026

Compromise of tj-actions/changed-files Exposed CI Secrets in GitHub Actions

The popular GitHub Action tj-actions/changed-files was compromised in a software supply-chain attack that redirected multiple release tags to a malicious commit, 0e58ed8671d6b60d0890c21b07f8835ace038e67, causing affected workflows to dump CI secrets into GitHub Actions logs. Early reporting indicated that all versions might be affected because tags in the repository had been moved to the attacker-controlled commit, prompting maintainers and defenders to urge organizations to immediately stop using the action, review workflow runs, and rotate any credentials that may have been exposed. GitHub later tracked the incident as CVE-2025-30066, and the project retagged releases and published v46.0.1 with guidance to pin only to a known-safe immutable commit.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

7 events · Mar 14, 2025 – Mar 26, 2026
  1. Mar 26, 20268mo ago

    Semgrep identifies and patches an exploitable GitHub Action internally

    During an internal response described by Semgrep, the company rescanned publicly invocable GitHub Actions, found at least one exploitable action in its own environment, and patched it. The effort was part of a broader review prompted by compromises affecting peer security vendors.

    Security Companies Under Attack: Defense in the Agentic Era | Semgrep
  2. Jan 24, 202610mo ago

    Malicious commit introduced into tj-actions/changed-files

    A malicious commit, 0e58ed8671d6b60d0890c21b07f8835ace038e67, was present in the tj-actions/changed-files repository and later identified as the commit to which compromised tags pointed.

    Github
  3. Mar 14, 20252y ago

    tj-actions retags releases and publishes v46.0.1

    Following the compromise, tj-actions retagged releases and published version 46.0.1, with guidance to pin to a known-safe immutable commit. This was the maintainer's remediation step for affected users.

    🚨 Popular GitHub Action tj-actions/changed-files is compromised | Semgrep
  4. Mar 14, 20252y ago

    GitHub publishes advisory for CVE-2025-30066

    Semgrep later reported that GitHub published an advisory for CVE-2025-30066 covering the tj-actions/changed-files compromise. This formalized public vulnerability tracking for the incident.

    🚨 Popular GitHub Action tj-actions/changed-files is compromised | Semgrep
  5. Mar 14, 20252y ago

    Malicious gist used in the attack chain was removed

    A later update in Semgrep's coverage stated that the malicious gist used in the tj-actions/changed-files attack chain had been removed. This disrupted part of the attacker infrastructure involved in the compromise.

    🚨 Popular GitHub Action tj-actions/changed-files is compromised | Semgrep
  6. Mar 14, 20252y ago

    Semgrep warns all tj-actions/changed-files versions may be compromised

    On March 14, 2025, Semgrep published an alert stating that all versions were believed compromised because repository tags pointed to the malicious commit 0e58ed8. The post warned that the action attempted to dump CI secrets to workflow logs and urged organizations to stop using it, audit runs, and rotate secrets.

    🚨 Popular GitHub Action tj-actions/changed-files is compromised | Semgrep
  7. Mar 14, 20252y ago

    Issue reports multiple compromised tags in tj-actions/changed-files

    On March 14, 2025, a GitHub issue was opened reporting that multiple tags in tj-actions/changed-files were compromised. This publicly documented the tag compromise in the action's repository.

    Multiple tags in this action are compromised · Issue #2463 · tj-actions/changed-files
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Affected products

1 linked
Changed-Files

Organizations

1 linked
GitHub

Observables

1 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.