Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-30066: Embedded malicious code in tj-actions/changed-files

Published Mar 15, 2025 · Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.6High · v3.1
EPSS72.1%99th percentile
CISA KEVYesAdded Mar 18, 2025
In the wildActivePer CISA KEV
Vendor
tj-actions
IdentifiersCVE-2025-30066CWE-506 · Embedded Malicious Code

CVE-2025-30066 is a supply-chain compromise of the tj-actions/changed-files GitHub Action affecting releases before version 46. On March 14–15, 2025, version tags v1 through v45.0.7 were redirected to a malicious commit containing modified updateFeatures code. The payload executed a Python script that extracted secrets from GitHub Actions runner process memory and wrote them into workflow logs using double Base64 encoding. Remote attackers could recover exposed credentials by reading those logs, with public repositories particularly exposed because their logs were publicly accessible. The action was referenced by more than 23,000 repositories, but this does not establish how many executed the malicious revision or leaked secrets.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Sensitive CI/CD credentials could be disclosed, including AWS access keys, GitHub personal access tokens, npm tokens, and private RSA keys. Public workflow logs could make those credentials available to unauthenticated readers; private workflow logs could expose them to users with log access. Depending on the stolen credentials' permissions and validity, subsequent abuse could enable repository takeover, malicious package publication, cloud resource access, or other downstream supply-chain compromise. CISA added the vulnerability to its Known Exploited Vulnerabilities catalog following evidence of active exploitation.

Mitigation

If you can’t patch tonight, do this now.

If a verified clean version cannot be deployed immediately, disable or remove the action across all branches, or block it using GitHub Actions allow-list settings. Preserve affected workflow logs securely for forensic analysis before deleting exposed logs to limit further disclosure. Pin actions to verified full-length commit SHAs rather than mutable tags or branches, and separately assess transitive dependencies. Minimize workflow token permissions and secret availability, prefer short-lived credentials, and monitor workflow and audit logs for suspicious activity. Outbound network restrictions alone do not prevent this attack because secrets can be disclosed through workflow logs.

Remediation

Patch, then assume compromise.

Update tj-actions/changed-files to version 46.0.1 or a later verified clean release, preferably referenced by its verified full-length immutable commit SHA. Replace any workflow references to the malicious revision, including references on non-default branches. Review historical workflow executions for compromised action use and secret disclosure. Revoke and rotate all credentials potentially exposed to affected executions, and investigate subsequent use of those credentials. Maintainers restored affected tags, but updating references alone does not invalidate previously leaked secrets.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
tj-actionsChanged-Filesapplication
FAQ

Frequently asked questions

Is CVE-2025-30066 exploited in the wild?
Yes. As of Nov 12, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 18, 2025.
Is there a public exploit for CVE-2025-30066?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-30066, the earliest disclosed May 14, 2026.
Is there a patch for CVE-2025-30066?
Update tj-actions/changed-files to version 46.0.1 or a later verified clean release, preferably referenced by its verified full-length immutable commit SHA. Replace any workflow references to the malicious revision, including references on non-default branches.
What products are affected by CVE-2025-30066?
tj-actions Changed-Files.
How severe is CVE-2025-30066?
CVE-2025-30066 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 72.1% (99th percentile) as of Nov 12, 2026.
Activity feed

Recent activity

31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
socket blogNews · Nov 3, 2026Hardening GitHub Actions Against Outside Threats | SocketA supply-chain compromise of tj-actions/changed-files redirected mutable version tags to credential-stealing code. Pipelines executing the compromised action exposed runner credentials through build logs, which were publicly readable for public repositories. Roughly 23,000 repositories referenced the action; repositories pinned to unaffected commit SHAs avoided the malicious tag changes.Read more ↗codebyNews · Jul 12, 2026Megalodon: атака на цепочку поставок GitHub - разборActively exploited supply-chain vulnerability/compromise involving the GitHub Action tj-actions/changed-files, where mutable version tags were repointed to a malicious commit, causing downstream workflows to execute poisoned action code.Read more ↗codebyNews · Jul 11, 2026Атаки на agentic AI пайплайны через GitHub issuesA high-severity supply-chain compromise involving tj-actions/changed-files, categorized as embedded malicious code and affecting more than 23,000 repositories.Read more ↗codebyNews · Jul 9, 2026CVE-2026-45131: уязвимость GitHub Actions - секреты CI/CDУязвимость в tj-actions/changed-files, приведённая как связанный пример аналогичных CI/CD и GitHub Actions supply-chain рисков; отмечена как эксплуатируемая в дикой природе и включённая в CISA KEV.Read more ↗
+12 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity11Community discussion across Reddit, Mastodon, and other social sources.