GitHub is investigating unauthorized access to their internal repositories (twitter.com)

209 points by splenditer 4 hours ago

starkeeper a few seconds ago

this is so amazing and brilliant display of the enshitification wow they won't fire the right people gauranteed maybe a slightly smaller ``bonus``

vldszn 3 hours ago

GitHub: "We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity."

TZubiri 2 hours ago

It reminds me of the famous "mistakes were made" Nixon quote.

"We are investigating unauthorized access" sounds much better than "we've been hacked"

vldszn 2 hours ago

Exactly =)

tiffanyh 2 hours ago

Is Twitter/X the right channel to announce a security event like this?

I ask because I don’t see anything posted on their official blog or status page.

https://github.blog/

https://www.githubstatus.com/

niyikiza 9 minutes ago

Probably the best option after sending a mass email when customers need to take action. The status page is for reliability issues impacting end users & the blog is for in-depth analysis.

cebert 2 hours ago

It’s a very popular messaging platform for tech enthusiasts.

yallpendantools an hour ago

So? Is this where your corporate paying clients should find out about an issue of this severity?

Not to mention Twitter is not an open platform anymore! (A) I'm an employee in an organization paying for Github. (B) I don't have a Twitter account. I already have a Github account because of (A). Why should (B) stop/delay me from getting official comms about this?

zdragnar 17 minutes ago

insanitybit an hour ago

uzyn 3 hours ago

The security issue aside, seeing more companies push announcements like these on X as the only official source is a trend I'm not sure I like.

I can understand the rationale, this feels lighter and not something that belongs on status.github.com or the blog. Maybe what's actually missing is an official channel for ephemeral stuff on a domain they own, somewhere between a status page and a tweet? Just sharing an observation.

niyikiza 8 minutes ago

My understanding is that when it's something that requires user action they'd directly send comms to customers.

bananamogul 5 minutes ago

I have a hard time believing this because there was never enough GitHub uptime to carry out the attack.

keyle 2 hours ago

This is bad. If they came out announcing this, without a long winded explanation and further details, it's because they're staring at a bottomless pit and they haven't put the lid on it yet.

For a Fortune 100, to go out of your way to spook investors is the least desirable approach.

eli 2 hours ago

Letting people know promptly is also the right thing to do and probably mandated by (at least some) customer contracts. You can't tell just some people; it would leak anyway.

vldszn 3 hours ago

- Use Static analysis for GHA to catch security issues: https://github.com/zizmorcore/zizmor

- set locally: pnpm config set minimum-release-age 4320 # 3 days in minutes https://pnpm.io/supply-chain-security for other package managers check: https://gist.github.com/mcollina/b294a6c39ee700d24073c0e5a4e...

- add Socket Free Firewall when installing npm packages on CI https://docs.socket.dev/docs/socket-firewall-free#github-act...

keyle 2 hours ago

The only way to 'harden your github actions' is to not use github actions.

vldszn 2 hours ago

Makes sense tbh :)

robbiet480 2 hours ago

Thanks for making me aware of zizmor, just ran and fixed all issues on our core repos.

vldszn an hour ago

You are welcome! Recently discovered it and found it genuinely useful. Fixed a bunch of issues in my workflows too :)

benoau 3 hours ago

You also need to make sure you take care using PR titles and descriptions in your GHA because if they contain `text` it *may be executed lmfao.

edited: not "will", may depending on your GHA

CGamesPlay 3 hours ago

Can you cite this? It's not YAML execution syntax, surely Github doesn't do it, the only vector I can see is if you put it unquoted into a shell script inside of a GHA yaml.

theteapot 2 hours ago

benoau an hour ago

vldszn 3 hours ago

Maybe zizmor could catch this https://github.com/zizmorcore/zizmor but not sure 100%

insanitybit an hour ago

buryat an hour ago

Sympathy to engineers and everyone at github, it's good that they're being open even if findings are limited. I'm sure they will figure out the root cause and will publish results to be a learning experience for everyone else

dijksterhuis 3 hours ago

killingtime74 2 hours ago

Time to switch to Gitlab, Bitbucket or self-hosted

MallocVoidstar 2 hours ago

https://pbs.twimg.com/media/HItbXhvW4AAMD8W?format=jpg&name=...

All of their repos have been copied and are up for sale. Attackers are TeamPCP, the creators of the Shai-Hulud malware.

mpetrovich an hour ago

If that’s true and they do intend on shredding their copy on sale, what stops GitHub from buying it back themselves? (through a proxy, obv)

neom a minute ago

Nothing, this is one of the most common types of ransomware going on right now, exfiltration only extortion.

ferguess_k an hour ago

I probably wouldn't believe that "shredding". Also there will be legal consequences I think?

surrTurr an hour ago

"Someone broke into our house and we have no clue if they're still hiding under the bed or in the drawer. TV is gone."

mstank 3 hours ago

Is it just me or is this happening way more frequently in the last 4 or 5 months? Coincidently around the same time the models got a lot more capable?

insanitybit an hour ago

I think AI has helped to a degree. I think a lot of people have known about massive gaps in security, but it's been a sort of "why would I?" and a gap that didn't feel worth hopping for attackers.

The gap is smaller now.

I've been talking about package worms for... fuck, a decade. Insane. I've even thought about publishing one to prove a point but, well, it's illegal obviously. And ethically questionable.

Someone just vibecoded up what we've all known was possible for a long, long time. Just like a lot of other vibe coded projects.

I remember talking to a malware author a long time ago and I think this would have been exactly what he would have loved. He liked building custom C2 protocols, tiny malware, etc, but when we discussed a particular idea for owning massive amounts of infrastructure his response was basically "that's a lot of effort to get a krebs article and FBI attention". Now it's not so much effort!

tom_ 3 hours ago

It's more likely that it isn't coincidental at all: software development-oriented LLMs became a lot better towards the end of 2025, and so there's a non-zero chance that people are using them to find new security exploits.

(People are not sleeping on this and it is not something people have failed to notice. I don't use LLMs at all and even I have noticed it - largely because there is approximately nobody that isn't talking about it.)

tptacek 2 hours ago

There is a 100% chance that people are using LLMs to find vulnerabilities and build exploits. If it was possible for something to be a 101% chance, that's what it would be.

tom_ an hour ago

OptionOfT 2 hours ago

I think the other side is much more important. With company mandates to use AI as much as possible, there has been a deluge of low-quality PRs. Everybody is feeling tired from reviewing those, and quite possibly numerous security issues have been introduced since.

tom_ an hour ago

skydhash an hour ago

guluarte 2 hours ago

I heard an engineer at Anthropic was submitting 150 PRs per day. That's one PR every 5 to 10 minutes, so you can guess the level of review and quality control involved.

tomrod 37 minutes ago

I have days with those kinds of PRs. Usually because I'm too lazy to check color compatibility outside the browser.

bob1029 3 hours ago

I think it's more about the popularity than the capability. The chances you might accidentally put a Github access token into an undesired security context goes up dramatically when you actually create and use one on a regular basis. The developers at GH are certainly using these tools just like the rest of us.

waynesonfire 3 hours ago

Are they required to announce that they're being hacked in real time?

tonetegeatinst 3 hours ago

Microsoft owned so many a CYA to explain why the liability insurance goes up to investors?

syngrog66 3 hours ago

between all the Linux LPEs and Claude's known security flaws, alone, I'd be shocked if Github and Microsoft hadnt gotten hacked by now. reasonable bet we mainly hear it when big shops get bit

TZubiri 2 hours ago

Before 2026 I hosted client code on GitHub, now it feels suboptimal, code is both an intellectual property asset and security risk. Especially if the company is software based, self-hosting your code just has a much better risk profile for almost no cost.

It's also one of those things that warms your team up and gets them ready for actual work, a team that has to self host their git and other infra, like self-hosting DNS servers with bind, will have a much better work ethic than engineers who click buttons on a SaaS and conflate their role as users of a system instead of admins of one.

Additionally, using github actions, and relying on Pull Requests (Tm) (R) (C) has always been (useful) vendor lock in (and a security risk in case of GH Actions). It wasn't enough to lock down a choice, but it tilts the balance in favour of less dependencies, which with the increase of CVEs and supply chain vulns, seems to be the name of the game for this new era. Build it in house, ignore the dogma.

kiernanmcgowan 3 hours ago

Mythos has broken containment