Better MC modpacks shipped Fracturiser malware

Better MC mattered because it was a modpack, not a single small mod. No attacker logged into Luna Pixel Studios' account. A developer there tried out one of the malicious uploads, fractureiser infected the jars on that machine, and the studio published the result as trusted bundles. The named affected scope included Better MC Forge BMC3, Better MC Forge BMC2, and Better MC Fabric, packages that pulled together many mods under a familiar project name, so the malicious upload inherited trust from both the modpack brand and its dependency graph.

Fractureiser used the Minecraft loader path as execution. Once a poisoned JAR was loaded, the staged malware reached beyond the game and targeted host data on Windows and Linux, including secrets useful for accounts and for further spread.

The cleanup problem was therefore not just "remove one mod." Players had to treat the whole affected modpack install as suspect, then scan for active infection and for dormant JARs that could restart the chain later.

This record stays separate from the campaign because Better MC was one of the high-signal package scopes. The campaign explains the shared malware; this record preserves the concrete releases players were told to remove and scan around.