Live data from Hacker News

GitHub is investigating unauthorized access to their internal repositories

twitter.com

171–180 of 359 posts

Re: GitHub is investigating unauthorized access to their internal repositories

#171

That's the reason I stopped installing random extensions and even themes in VS Code, they are too dangerous.

I just moved to Zed (zed.dev). Has everything I need

unfortunately it's not anprroved tool in many companies. VSCode's new Agents window is quite similar to zed's Parallel Agents UI though.

Re: GitHub is investigating unauthorized access to their internal repositories

#172

Why are half the comments in that thread AI generated? What value do they think they bring?

Cookie points, interaction, favorites, Super Mario Bros stars.

Money is a small thing to spend for all the fame it brings. Remeber: Value trumps everything, an everyone wants it. From investors to end users. /s

Re: GitHub is investigating unauthorized access to their internal repositories

#173

Which extension was it?

If I had to guess it is the NX console extension that was compromised yesterday. But I’m not 100% sure. https://github.com/nrwl/nx-console/security/advisories/GHSA-...

NX again??

This isn't the first time their plugin has led to RCE...

Re: GitHub is investigating unauthorized access to their internal repositories

#174

That's the reason I stopped installing random extensions and even themes in VS Code, they are too dangerous.

I just moved to Zed (zed.dev). Has everything I need

I really need to find the time to properly test Zed. I'm mainly using PHP Storm and I love what it can do, especially when it comes to code discovery and auto-completion. I'm not a huge fan of having a bloated toolbox, I never use PHP Storm's included terminal or database browser.

Zed was super impressive when I first started it, but I don't know yet how it compares with PHP Storm.

Re: GitHub is investigating unauthorized access to their internal repositories

#176

Why did one developer have access, even if read-only, to more than 3,800 internal repos?

Devs not having read access to all code seems like a massive org smell. What’s worse, in many cases not having access doesn’t just prevent you from seeing it it also prevents you from knowing it exists. Now you don’t know what to ask for, who to ask, or what to not implement again. There is no security risk that you could use to convince me that ”devs should only have access to code they need to modify”.

Yeah I worked in a company that blocked access to their main (terrible) product from some devs. They are not doing too well...

Re: GitHub is investigating unauthorized access to their internal repositories

#177
post #153
post #71

GitHub: " Our current assessment is that the activity involved exfiltration of GitHub-internal repositories only. The attacker’s current claims of ~3,800 repositories are directionally consistent with our investigation so far." Oof https://xcancel.com/github/status/2056949169701720157

directionally, how bad is this ?

Directionally? Yes, bad

Re: GitHub is investigating unauthorized access to their internal repositories

#178
post #168

Earlier quoted context omitted.

This comment reminds me of a joke where the punchline is that a person is so poor that burglars break in to their house and leave money. Similarly, I could see ransomware groups hacking in and feeling bad for GH so they improve a few things to help them get to at leave nine fives of uptime.

Just in case you are not aware, a joke loses its fun factor if you explain it.

But they become fun again when someone points that out.

Re: GitHub is investigating unauthorized access to their internal repositories

#179

Why did one developer have access, even if read-only, to more than 3,800 internal repos?

Sounds like a great way to have outages because you can’t tell what legacy features are still in use or not. Or even worse, not being able to ever refactor or clean up because you have no means to discover your dependencies.

Re: GitHub is investigating unauthorized access to their internal repositories

#180
post #144

Earlier quoted context omitted.

Devs not having read access to all code seems like a massive org smell. What’s worse, in many cases not having access doesn’t just prevent you from seeing it it also prevents you from knowing it exists. Now you don’t know what to ask for, who to ask, or what to not implement again. There is no security risk that you could use to convince me that ”devs should only have access to code they need to modify”.

in my org, devs don’t have access to customer data directly, and sysadmins don’t have access to modify code. It’s a simple rule from a simpler time, to limit the risk of total compromise.

Repos should not contain customer data.
Post reply on HN