▲ 8 ▼ Megalodon chums the waters in 5.5K+ GitHub repo poisonings (www.theregister.com) submitted 5 months ago by yogthos@lemmy.ml to c/security@lemmy.ml 2 comments fedilink hide all child comments
[–] zdhzm2pgp@lemmy.ml 1 point 5 months ago (1 child) Um, so, sorry for the potentially dumb question, but do I need to worry about this? permalink fedilink source hideshow 1 child comment replies: [–] yogthos@lemmy.ml [S] 4 points 5 months ago The exploit affects repository owners if they merge the malicious commit, their CI/CD pipeline gets infected, and their cloud credentials, SSH keys,GitHub tokens, and etc., are stolen. Anyone working on compromised repositories or using CI/CD variables could have their credentials exfiltrated. If you are not a repository owner or contributor to affected repos then your direct risk is likely low. The article lists 5,561 infected repositories, so if you don't contribute to or use any of those repos (the full list was published by SafeDep), you're fine. permalink fedilink source parent
[–] yogthos@lemmy.ml [S] 4 points 5 months ago The exploit affects repository owners if they merge the malicious commit, their CI/CD pipeline gets infected, and their cloud credentials, SSH keys,GitHub tokens, and etc., are stolen. Anyone working on compromised repositories or using CI/CD variables could have their credentials exfiltrated. If you are not a repository owner or contributor to affected repos then your direct risk is likely low. The article lists 5,561 infected repositories, so if you don't contribute to or use any of those repos (the full list was published by SafeDep), you're fine. permalink fedilink source parent
all 2 comments