GitHub is investigating unauthorized access to their internal repositories

Re:GitHub is investigating unauthorized access to their inte... by DanielHB on Wednesday May 20, 2026 @08:08AM (#48206407)

LLMs can't really parse compiled code to find exploits, maybe code in scripting languages (python, js, etc) even if minified. So I don't quite agree with you, having access to the source can definitely help find exploits even in pre-LLM days.

[ Parent | on HN ]

Re:GitHub is investigating unauthorized access to their inte... by pixl97 on Wednesday May 20, 2026 @08:49AM (#48206830)

Pretty much everyone disagrees with you, especially when you add in decompiler tools to the LLM.

[ Parent | on HN ]

Re:GitHub is investigating unauthorized access to their inte... by Yiin on Wednesday May 20, 2026 @10:01AM (#48207969)

how to say you haven't tried llms since 2023 without saying it, that's quite literally one of the things they excel at

[ Parent | on HN ]

Re:GitHub is investigating unauthorized access to their inte... by ammar2 on Wednesday May 20, 2026 @12:07PM (#48209994)

Also, the Github enterprise code is "obfuscated" but it uses a trivially reversible method just meant to be a minor roadblock. After you get past that you get the full ruby source code, no minification or anything.

For a while the key was literally:

> This obfuscation is intended to discourage GitHub Enterprise customers from making modifications to the VM. We know this 'encryption' is easily broken.

[ Parent | on HN ]