CVE-2025-30066 tj-actions changed-files GitHub Action: hidden backdoor
In plain words: The software was shipped with hidden malicious code inside it. Whoever planted it has secret access to every copy.
Confirmed exploited by CISA on · US federal patch deadline Apr 8, 2025
What to do
- Install tj-actions's security update for changed-files GitHub Action. If no update exists, follow the vendor's workaround or stop using the product until one ships.
- Install system updates the day they come out — most phone zero-days are fixed in a point release.
- Restart your phone every few days; some spyware does not survive a reboot.
- If you are a journalist, activist, lawyer, politician or executive, turn on Lockdown Mode (iPhone) or Advanced Protection (Android).
Who is affected
Could reach you. This one is aimed at devices or apps of the kind people own.
What's at risk: Messages, photos, location, microphone and camera. The most serious ones are "zero-click": no tap needed from the owner. They are usually used as spyware against a small number of chosen people.
The details
- Official name
- tj-actions/changed-files GitHub Action Embedded Malicious Code Vulnerability
- Product
- tj-actions changed-files GitHub Action
- CISA description
- tj-actions/changed-files GitHub Action contains an embedded malicious code vulnerability that allows a remote attacker to discover secrets by reading Github Actions Workflow Logs. These secrets may include, but are not limited to, valid AWS access keys, GitHub personal access tokens (PATs), npm tokens, and private RSA keys.
- Type of flaw
- Hidden backdoor (CWE-506)
- Confirmed exploited
- Mar 18, 2025
- US federal patch deadline
- Apr 8, 2025
Ask Cleus about it
Ask about a vulnerability, an update, a weird message, or the news. Plain-word answers, free, no account.
Answering about CVE-2025-30066 ·
Questions about CVE-2025-30066
Is CVE-2025-30066 being exploited?
Yes. CISA added CVE-2025-30066 to its Known Exploited Vulnerabilities catalog on Mar 18, 2025, which means there is reliable evidence of real-world attacks.
How do I fix CVE-2025-30066?
Install tj-actions's security update for changed-files GitHub Action. If no update exists, follow the vendor's workaround or stop using the product until one ships. Install system updates the day they come out — most phone zero-days are fixed in a point release.
Am I affected by CVE-2025-30066?
Only if you use tj-actions changed-files GitHub Action. This one is aimed at devices or apps of the kind people own.