←back to thread

Ruby Central's Attack on RubyGems [pdf]

(pup-e.com)
659 points jolux | 4 comments | 19 Sep 25 08:09 UTC | HN request time: 0.701s | source
1. loloquwowndueo ◴[19 Sep 25 14:15 UTC] No.45301919[source]▶
Totally reads like post-facto CYA. they could have communicated this to the maintainers internally beforehand instead of blindsiding them.
replies(1): >>45303795 #
2. downrightmike ◴[19 Sep 25 16:51 UTC] No.45303795[source]▶
The NPM breach was an email that stated the dev needed to update their MFA by the next day in order to keep their access.

If you're arguing that is what ruby central should have done, that's a social engineering attack.

replies(2): >>45304659 #>>45307157 #
3. loloquwowndueo ◴[19 Sep 25 18:10 UTC] No.45304659[source]▶
It’s entirely possible to distinguish between legit internal communication and a phishing email. (It gets harder and harder every day but ultimately still possible)
4. mrinterweb ◴[19 Sep 25 21:54 UTC] No.45307157[source]▶
How would a heads up email look like a phishing email? Blindsiding the maintainers like this is just cruel.