37
New Gitloker attacks wipe GitHub repos in extortion scheme
(www.bleepingcomputer.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Jun 2024
37 points (100.0% liked)
Cybersecurity
5677 readers
112 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub
Notable mention to !cybersecuritymemes@lemmy.world
founded 1 year ago
MODERATORS
Funny thing is… the nature of git repos is when you work on the code base the first step is cloning it. The more contributors you have the more clones. The process naturally propagates distributed backups, albeit some being liable to be more out of date than others. I’d be interested in learning how successful this actually is for the attackers over time. I expect most maintainers will simply take the lesson learned, update their repo’s security and access controls, and restore the code base from the most recent local clone.