RatOrNot
All guides

Basics

What is a Minecraft RAT?

Last updated November 16, 2026

A RAT, or Remote Access Trojan, is a program that lets someone else control or spy on your computer. In the Minecraft world the term is also used loosely for any malicious mod that steals data, even when it never offers remote control at all.

In practice a “Minecraft RAT” is a mod .jar that looks like a normal Fabric, Forge, NeoForge or Quilt mod but carries extra code that runs when the game starts. Because a mod runs with your own user privileges, that code can read your files, use your network connection and start other programs. This guide explains what the code does, how it reaches players and what gives it away.

RAT, stealer, loader: three different jobs

The names get mixed up, and many real samples do more than one job:

  • Stealer. Collects credentials and sends them out once, usually at startup. Typical targets are the Minecraft session token, Discord tokens, browser logins and cookies, and crypto wallet files.
  • Loader (downloader). Does very little itself. It fetches a second program from a remote server and runs it, which lets the attacker change the payload at any time. A small, clean-looking first stage is the point.
  • RAT. Stays connected to a command server and accepts instructions, such as running a program, taking a screenshot, reading the clipboard or uploading a file.

RatOrNot does not care which label fits. It looks for the behaviours behind them, listed on what RatOrNot detects.

Why Minecraft mods make a good carrier

Mods are ordinary Java programs. There is no permission prompt when a mod loads, and Java's old security manager is no longer used, so nothing separates the mod from the rest of your user account. See what a mod jar can and cannot do for the details. Mods are also shared constantly, often between people who trust each other, which suits an attacker.

What the code actually does

Malicious behaviour is not magic. It is a short chain of standard Java calls. Three simplified examples, with the host defanged and invented for illustration:

  • Session theft. MinecraftClient.getInstance() then getSession() then getAccessToken() (Yarn names; Mojang and obfuscated names differ), the value goes into a string, and a URL.openConnection() call POSTs it to a webhook such as hxxps://discord[.]com/api/webhooks/<id>/<token>.
  • Loader. URL.openStream() reads bytes from hxxp://files[.]example[.]invalid/a.bin, and a custom ClassLoader.defineClass turns them into running code. Alternatively the bytes are written to a temp file and started with Runtime.exec("java -jar ...").
  • Remote shell. A Socket connects to a host and port, a loop calls BufferedReader.readLine(), and a switch over the received text dispatches to ProcessBuilder, Robot.createScreenCapture or a file upload.

None of these calls is suspicious alone: update checkers use URL, screenshot mods use Robot. The danger is in the combination and in what the data is. That is why RatOrNot follows values from where they are read to where they go.

How they spread

Most infections come from jars shared outside the large, moderated mod sites: Discord servers, file-sharing links, YouTube descriptions, “free cheat client” downloads and pirated modpacks. Current campaigns such as WeedHack rely on exactly these channels, often with fake mod names or repackaged real mods.

Occasionally a malicious upload or a compromised author account reaches an official platform. The 2023 fractureiser outbreak is the best-known case, which is why checking is worthwhile even on trusted sites. Where you download matters a lot; see where to download mods safely.

Warning signs

  • A mod that asks you to disable your antivirus. Real mods never need this.
  • A client-side mod with no public source code, no project page and no release history.
  • A tiny jar that claims to be a large, well-known mod, or a familiar name from an unfamiliar author.
  • A download that arrives as a Discord direct message or a link from someone you do not know well.
  • Unexpected network activity, new files or unfamiliar startup entries after you launch the game.
  • Your accounts logging in from places you have never been.

What a clean mod looks like by comparison

Plenty of normal mods make web requests, read config files, use reflection to talk to other mods or bundle networking libraries. Those are expected. A mod that reads only its own config/ folder, contacts only its own update API and shows your username in a menu is behaving as designed. The guide on false positives explains how to tell the difference.

What to do

  1. Scan the file with the RatOrNot scanner before it goes into your mods folder.
  2. Read the evidence for any flag, not only the verdict colour. The routine is in how to check if a mod is safe.
  3. If you already ran something doubtful, follow what to do if you ran an infected mod, starting with your account passwords from a clean device.

Static analysis reads a jar without running it, so a scan is safe to do on a suspect file. It is still an assessment, not a guarantee. Read how RatOrNot works for what it can and cannot see.