this post was submitted on 31 Mar 2024
455 points (98.3% liked)

Open Source

30950 readers
495 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

Thought this was a good read exploring some how the "how and why" including several apparent sock puppet accounts that convinced the original dev (Lasse Collin) to hand over the baton.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 143 points 7 months ago (2 children)
[–] [email protected] 96 points 7 months ago (4 children)

Imagine finding a backdoor within 45 day of it's release into a supply chain instead of months after infection. This is a most astoundingly rapid discovery.

Fedora 41 and rawhide, Arch, a few testing and unstable debian distributions and some apps like HomeBrew were affected. Not including Microsoft and other corporations who don't disclose their stack.

What a time to be alive.

[–] [email protected] 21 points 7 months ago

Arch was never affected, as described in their news post about it. Arch users had malicious code on their hard disks, but not the part that would have called into it.

[–] [email protected] 17 points 7 months ago

Before resting on our laurels, we should consider it's possible it's more widespread but just not being disclosed until after it's patched.

It would be wise to be on the lookout for security patches for the next few days.

[–] [email protected] 10 points 7 months ago (1 children)

Consider this the exception to the rule. There's no reason we should assume this timeline is the norm.

[–] [email protected] 2 points 7 months ago

True. Though remarkable is still remarkable.

Notably, the timeline post-discovery is still stellar, regardless of Microsoft/GitHub cock-blocking analysis.

[–] LiveLM 53 points 7 months ago* (last edited 7 months ago)

Disguising the virus as a corrupted test file then 'uncorrupting' it is crazy