Detection
Downloaders and loaders hidden in Minecraft mods
A loader is a small first stage. The mod itself looks nearly empty because the real payload is fetched or decrypted only after it runs.
What the behaviour looks like
Typical shapes: open a URL, read all bytes, turn them into a class with defineClass in a custom class loader; or point a URLClassLoader at a remote address; or save a file to a temp folder and start it with java -jar. Some builds decrypt an embedded blob first, which hides the download from a simple string search.
Rules in this family
load.define-downloaded: bytes from the network are defined as a class.load.define-decrypted: decrypted bytes are defined as a class.load.download-then-run: a downloaded file is written and then executed.load.run-jar: another jar is launched.load.url-classloader-network: a class loader is pointed at a remote URL.exec.download-command: a shell command downloads a file.exec.native-load-network: a native library is loaded after a network fetch.
Not every download is bad: update checkers fetch a small JSON file and show a message. The difference is that a loader turns downloaded bytes into running code.
Related reading
How malicious mods hide, what jar files can do and LoaderClient.
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.
