Live data from Hacker News

GitHub is investigating unauthorized access to their internal repositories

twitter.com

341–350 of 359 posts

Re: GitHub is investigating unauthorized access to their internal repositories

#341
post #338

Earlier quoted context omitted.

Everytime it is BreachForums: https://breached.st/threads/internal-github-source-code.8739...

What is the hell is muslims-of-github.tar.gz ?! I guess nebula is the new PRISM. What is `newly-packaged-malware` ?! I'm sorry for Sophie.

> What is the hell is muslims-of-github.tar.gz ?!

Is Github keeping a list of Muslims in their platform?

That's horrifying

Re: GitHub is investigating unauthorized access to their internal repositories

#342
post #338

Earlier quoted context omitted.

Everytime it is BreachForums: https://breached.st/threads/internal-github-source-code.8739...

What is the hell is muslims-of-github.tar.gz ?! I guess nebula is the new PRISM. What is `newly-packaged-malware` ?! I'm sorry for Sophie.

Probably a repo for the Muslim affinity group within GitHub. You'll also see repos for the blacktocats, octoqueer, octogatos, christian-hubbers. Everything in GitHub has a repo.

Re: GitHub is investigating unauthorized access to their internal repositories

#343
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 ?

Using 3,800 as a direction is an abuse of English.

Re: GitHub is investigating unauthorized access to their internal repositories

#344
post #259

Earlier quoted context omitted.

Well yeah, they need that to do maintenance work. They can see my company's private repos from our enterprise contract, so they can absolutely see your personal ones.

Your support people seeing your account and your repos is different from arbitrary support people seeing everyone's private repos.

Not just support people, and not just the customers they serve, any employee can go willy nilly into any repo.

Re: GitHub is investigating unauthorized access to their internal repositories

#345
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 ?

down

Re: GitHub is investigating unauthorized access to their internal repositories

#346
post #252

If they do leak it all, these are the first one's im digging into out of curiosity 3329:-rw-r--r-- 1 root root 62971493 May 18 22:52 spam-investigations.tar.gz 3330:-rw-r--r-- 1 root root 7915019 May 18 22:55 spamops.tar.gz 680:-rw-r--r-- 1 root root 306146 May 18 23:14 copilot-abuse-dashboard.tar.gz 681:-rw-r--r-- 1 root root 219637 May 18 23:03 copilot-abuse.tar.gz 2245:-rw-r--r-- 1 root root 55838 May 18 23:14 le-…

Full LLM-generated repository-purpose guesses: https://github-repos-analysis.pagey.site

Re: GitHub is investigating unauthorized access to their internal repositories

#348

Earlier quoted context omitted.

Except extensions.

In this day and age, and extensión is the thing is ask my local AI to do for me. They are very simple, self contained code that can be crappy as I'll run it locally. Browser extensions have been a great playground for me.

You're preaching to the choir, I've personally done 30+ custom chrome extensions and that was pre-AI.

Nowadays it's mostly tamper-monkey scripts when I just want to rearrange a website's DOM. I do those with Claude and it one-shots them more often than not.

Re: GitHub is investigating unauthorized access to their internal repositories

#349
post #334

Earlier quoted context omitted.

In the age of LLMs, vetting can even be done in a CI/CD. What's the big deal?

Token use? Non-deterministic outcomes?

Whatever findings they come up with, must be formalized to avoid non-determinism.

Draft an integration test of every finding.

The malicious extension makes calls to haxx0r.net? Draft a case in your integration test that intercepts this.

Re: GitHub is investigating unauthorized access to their internal repositories

#350
post #334

Earlier quoted context omitted.

Token use? Non-deterministic outcomes?

Whatever findings they come up with, must be formalized to avoid non-determinism. Draft an integration test of every finding. The malicious extension makes calls to haxx0r.net? Draft a case in your integration test that intercepts this.

But why will LLMs get this right when Web-of-Trust and blacklists didn’t? For a long time we’ve had different heuristics to detect abuse, and it’s always been a losing battle.

E.g. an extension that sends requests to an IP. Do you block all network access? IP ranges? Well, we’ve had firewalls for ages, hackers still craft successful vectors.

Post reply on HN