"We have checked our own environments thoroughly and found no traces of compromise. We suspect this may be part of the broader GitHub infrastructure breach carried out by the TeamPCP hacking group in May 2026: <a href="https://techcrunch.com/2026/05/20/github-says-hackers-stole-data-from-thousands-of-internal-repositories/" rel="nofollow">https://techcrunch.com/2026/05/20/github-says-hackers-stole-...</a>"<p>Greater HN collective, please help me metaphorically double-click on this. I've poked around a bit but didn't find out much more than the given link. What are we concerned about the hack possibly having accomplished?<p>Because stealing repos is bad enough... but are we saying it's possible that commits can now magically appear in repos from hackers? I don't want to raise any alarms if I'm misreading this or if we're early in the news cycle, but if that's possible, I and a lot of other people reading this need to have some immediate conversations with a lot of people. So... is that what this is saying? Or am I misreading it? I sure hope so.
Don't use github actions. Don't use toolchains that auto execute stuff.<p>Simple as that, because that's the attack surface.<p><a href="https://cookie.engineer/weblog/articles/malware-insights-github-actions-script-injection.html" rel="nofollow">https://cookie.engineer/weblog/articles/malware-insights-git...</a><p>I wrote that article December 2024. Still ongoing, Microsoft. Best enterprise security practices, I suppose <i>shrugs</i> ...
I was impacted. found weird spam repos that later were deployed on cloudflare redirecting my domains.<p>meanwhile the gitea running on my metalbox for nearly a decade has seen no compromise and 100% uptime when cloudflare has gone down repeatedly<p>im rethinking the whole "go where crowd is" , while great from evolutionary point of view, its the complete opposite. Where the crowd gathers online is the most dangerous place.
We're working on an antiworm. One of our customers got affected.<p>Our tool already discovers infected repositories and mitigates/removes the implants from the filesystem.<p>Please revoke/rotate all your tokens and passwords that were used in the infected repositories, the worm is pretty sophisticated.<p><a href="https://github.com/Team-Rockstars-Security/antimiasma" rel="nofollow">https://github.com/Team-Rockstars-Security/antimiasma</a>
So in summary:<p>* GitHub's backwards priorities end up causing a hack on their systems.<p>* Hackers use their newly gained powers to compromise other people's repos.<p>* GitHub dectects compromised repo, and suspends the account of its maintainer, so they cannot warn nor act against it to protect or at least warn their community of users.<p>"I cause a fire, and later ban you for getting burned."<p>No wonder people are leaving.
Seems like it's similar to the attack reported in this other HN post: <a href="https://news.ycombinator.com/item?id=48409869">https://news.ycombinator.com/item?id=48409869</a>
Looking at the setup.js it seems to be an infostealer which posts the found details to a newly created github repo (on the victims account) or a command and control server. As far as I can tell it looks for github secrets and kubernetes cluster secrets.
[dead]