History
The fractureiser incident, explained
Fractureiser was a multi-stage piece of malware found in June 2023 inside mods and plugins uploaded to community platforms. It could steal credentials and infect other jars on the victim's machine, and it remains the most widely discussed malware incident in Minecraft modding.
This guide covers what it did, why it mattered and which of its techniques you should still watch for. A shorter summary with the detection rules that apply to it is on the fractureiser threat page.
What it was
The first stage was embedded in uploaded mods and plugins on community platforms, in some cases after the author's account had been compromised. When an infected mod ran, it contacted a remote server and downloaded further components. Those later stages were reported to target both Windows and Linux, to collect saved credentials and wallet data, and to infect other jars so the malware could survive and spread to anything the victim later shared.
How the stages fit together
Researchers working on the incident described a chain of stages, each fetched by the one before it. The names below follow the community write-up; consult the project's own repository for the authoritative technical detail.
- Stage 0 was the code injected into the mod itself. It was small and did one thing: fetch the next stage and load it. That is a loader, which is why a plain scan of the visible code could look almost empty.
- Stage 1 set up persistence and prepared the machine, using the usual per-platform mechanisms such as a startup entry on Windows or an autostart entry on Linux.
- Stage 2 was the part that went looking for other jars to modify.
- Stage 3 was the data-stealing payload, aimed at browser data, launcher and game accounts and crypto wallets, and it also monitored the clipboard for wallet addresses.
Why it mattered
- It spread through trusted channels: legitimate-looking mods on popular sites.
- It was self-propagating, so an infected player could pass it on to others without knowing.
- It was staged, so the first jar looked small and harmless and the real payload lived on a server.
- It crossed from game data to the whole machine: browser logins, wallets and other software.
The behaviours, in terms a scanner can see
Every stage relied on ordinary Java calls, which is what makes these patterns detectable without ever running the file:
- Remote code loading: bytes read from a URL and turned into code with
defineClass, or a class loader pointed at a remote address. See downloaders and loaders. - Self-replication: opening other files in the
mods/folder withZipFileorZipOutputStreamand writing a class into them. See persistence and self-spreading. - Persistence: writing to the Startup folder, a Run registry key, a scheduled task or an autostart file.
- Clipboard monitoring for wallet-like strings, a common stealer trick.
How the community responded
Mod authors, platform staff, launcher developers and security researchers worked together to analyse the samples, publish indicators of compromise, take down malicious uploads and write detection tools. A public investigation repository collected the findings, and several standalone checkers appeared within days. Platforms later tightened upload review and added more guidance for players.
Lessons that still apply
- Treat every jar as executable code, not as a harmless data file.
- Prefer files from authors with a visible history and public source.
- Scan new files before use, and rescan after updates. A compromised author account can turn a trusted mod into a carrier overnight.
- Remember that an infected mod folder is not just one bad file. Self-spreading code means you must check every jar, not only the one you suspect.
- If you suspect an infection, follow a full cleanup. See what to do if you ran an infected mod.
RatOrNot checks for the behaviours this kind of malware relies on: downloading and loading remote code, touching other jars, reading credential stores and persisting on the system. Newer campaigns reuse the same ideas; read about the current ones on the threats page.
