RatOrNot
All guides

Basics

What a mod jar can and cannot do

Last updated November 16, 2026

A Minecraft mod is not a texture pack or a save file. It is a program, and it runs with the same privileges as you. Nothing in Java or in the game separates it from the rest of your user account.

No sandbox

Java once had a security manager that could restrict code, mostly for applets. It was deprecated for removal and has been disabled in current Java versions, and Minecraft never used it to confine mods. A mod can therefore do anything your user account can do. Mod loaders do not ask for permissions either: a mod gets full access the moment the game loads it.

What a mod can do

  • Read and write files in any folder your account can access, including documents, browser profile folders and the launcher's account files.
  • Open network connections to any server, send data out and download files.
  • Start other programs and scripts, for example by launching a new Java process or a command line.
  • Load additional code from disk or the network and run it inside the game.
  • Read the game's internal state, including your session and chat, and change how the game works through mixins and hooks.
  • Capture the screen or clipboard through standard Java classes, and call native Windows functions through libraries such as JNA.
  • Change startup settings so that something runs again at the next login.

Most of these are useful: config files, update checks, screenshots and integration with other mods all need them. Malware uses the same abilities, which is why the question is always what a mod does with them.

What it cannot do on its own

  • Bypass operating-system permissions you did not already grant to your account. On Windows, installing for all users or changing protected system areas normally needs an administrator prompt, unless you run the game as an administrator, which you should avoid.
  • Access other accounts' files on a properly configured multi-user system.
  • Reach other computers on your network except through the network access your computer already has.

Your own account holds most of what attackers want, though: browser logins, Discord, the game session and wallets. A mod does not need administrator rights to steal those.

Is a jar dangerous before it runs?

A jar is just an archive until Java loads it. Opening it in an archive tool, or scanning it as RatOrNot does, does not run any of its code. The risk begins when the game, or someone double-clicking the jar, executes it.

Practical consequences

  • Trust matters more than technology here. Install mods from people you can verify.
  • Keep your accounts protected with two-step verification.
  • Use a separate user account or machine for anything you are unsure about, and do not keep saved logins in that account's browser.
  • Look at how to check a mod before using anything new, and scan the file first.

See what typical misuse looks like in what is a Minecraft RAT and in the behaviours listed on what RatOrNot detects.