How Coder avoided the tj-actions/changed-files
GitHub action compromise
#16993
matifali
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are aware of the recent security incident1 involving the
tj-actions/changed-files
GitHub Action, which affected over 23,000 repositories. This action contained malicious code that could expose CI/CD secrets by printing them in build logs.We are pleased to report that our repositories were not impacted. We achieve this by strictly pinning all GitHub Actions to specific commit hashes. This practice ensures our workflows run only the intended code, protecting against unauthorized changes.
For transparency, we maintain an OpenSSF Scorecard2 that shows our commitment to security best practices. We will continue to monitor and adapt our practices to keep our community safe.
Footnotes
https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised ↩
https://openssf.org/projects/scorecard ↩
Beta Was this translation helpful? Give feedback.
All reactions