@kkarhan
>it only affects #Windows Users
Wrong again! The malware was also specifically designed to infect Linux users as well.
>I could also say "Your fault for using a shitty govware - lol" but I think that's kinda assholeist at this point.
You already kind of tipped your hand about how smug and obnoxious about this whole situation when you failed to do a literal five second Google search for more information while pretending to be an expert on the situation.
>I do think it's #CurseForge who fucked up because it's their #API and toolchain and not the modders or users' faults based off the reports...
CurseForge's API had nothing to do with it. Firstly, please note that "Forge Mod Loader" and "CurseForge" are two entirely different entities, please. There's a reason CF isn't in the position to employ anything functional in terms of enforcing things like code signing and whatnot -- the base infra for MC modding is kind of a shitshow with non-deterministic builds and weird dependency fetching. This kind of shit would have, and could have, happened on Modrinth, but fractureiser targeted the more popular website, for incredibly obvious reasons.
Anyways, fracturiser C&C server is still down to this day and all the major distros have detectors for fracturiser malware now. It's old news. Stop being so smug about it, and maybe help out if it's such an easy problem to you.
Here's your sources, buddy.
https://github.com/fractureiser-investigation/fractureiser/blob/main/docs/tech.md
https://github.com/fractureiser-investigation/fractureiser/blob/main/docs/2023-06-08-meeting.md
https://github.com/fractureiser-investigation/fractureiser/blob/main/docs/timeline.md