Detection
Persistence and self-spreading mods
Persistence means the malware keeps running after the game closes. Self-spreading means it goes on to infect the other mods you have installed.
What the behaviour looks like
On Windows: a file written to the Startup folder, a Run key added with reg add, or a scheduled task. On macOS: a LaunchAgent. On Linux: an autostart entry. For spreading: open each jar in the mods folder as a ZIP, add a class, and rewrite it, which is how fractureiser multiplied.
Rules in this family
persist.startup-folder: Windows Startup folder.persist.registry-run: Windows Run registry key.persist.schtasks: a Windows scheduled task.persist.launch-agent: a macOS LaunchAgent.persist.linux-autostart: a Linux autostart entry.persist.mods-folder-jar: other jars in the mods folder are opened.persist.self-replicate: code is injected into other jars.
Related reading
fractureiser and fractureiser explained.
One finding is a lead, not a verdict. RatOrNot combines these signals and follows the call path from the mod entrypoint, so a mod that reads a value to display it scores very differently from one that sends it away. See false positives in jar scanners, or scan a mod now.
