Whoa, this is seriously messed up! Just finished reading an article about the compromised GitHub Action `tj-actions/changed-files`. Get this – over 23k repos were affected! That's a huge deal, right?
Turns out, CI/CD Secrets (think AWS Keys, Tokens, the whole shebang) were snatched. It's CVE-2025-30066 – a full-blown Supply Chain Attack!
So, what happened? Well, the attacker modified the code and tampered with the version tags. Then, the Action diligently packed Secrets into Build-Logs… ouch!
And why is this so bad? Supply Chain, folks! Open Source is fantastic, no doubt, but keeping things in check is absolutely crucial! It kinda reminds me of a Pentest we did where we nearly missed something...
Alright, here's what you gotta do: Update to 46.0.1 *immediately*! Plus, take a look at your workflows from the 14th-15th. I just had this issue pop up with a client... Update done, problem solved! Also, remember the Least Privilege Principle! Keep a close eye on Open Source stuff, always!
Open-Source Security is still incredibly important! You've got to take Supply Chain risks seriously! Because, security is a continuous process, not a product you just buy! It's like those customers who think ISO 27001 solves all their problems...
So, have you guys experienced similar horror stories? What tools do you use for Supply Chain Security? What are your biggest Open-Source nightmares? Share them below!