logoalt Hacker News

dawnerdtoday at 8:25 AM5 repliesview on HN

Everyone is blaming npm but GitHub should be put on blast too for allowing the repos to be created and not quickly flagged.

GitHub has a massive malware problem as it is and it doesn’t get enough attention.


Replies

baobuntoday at 10:46 AM

I would put blame on contemporary GitHub for a few things but this is not one of them. We need better community practices and tools. We can't expect to rely on Microsoft to content-filter.

princevegeta89today at 9:03 AM

I love! how Github, as a corporate company now owned by Microsoft, is directly tied to GoLang as the main repository of the vast majority of packages/dependencies.

Imagine the number of things that can go wrong when they try to regulate or introduce restrictions for build workflows for the purpose of making some extra money... lol

The original Java platform is a good example to think about.

show 2 replies
hiccuphippotoday at 3:58 PM

Pushing the data to Github was a blessing in disguise. A friend wouldn't have noticed he got caught if it didn't create a repo on his account. It would have been worse if it silently sent the data to some random server.

benatkintoday at 8:35 AM

They're part of the same company, but that's a good point. They both have mediocre security.

testdelacc1today at 9:19 AM

Wouldn’t have been that hard to write a rule that matches the repositories being created by this malware. It literally does the same thing to every victim.

show 1 reply