RatOrNot
All guides

How-to

How to check if a Minecraft mod is safe

Last updated November 16, 2026

Check where the file came from, who made it, and whether the file matches the official one, then scan it before it goes into your mods folder. No single check is perfect, but together they catch the large majority of malicious mods.

A mod is a program that runs with your own privileges (see what a mod jar can and cannot do), so vetting it is closer to vetting software than to vetting a texture pack. The routine below takes a few minutes.

1. Check where it came from

Download from the author's page on a moderated platform such as Modrinth or CurseForge, or from their public source repository. Be wary of re-uploads on random sites, even if the mod name is familiar. Fake mirrors and repackaged copies are a main way campaigns such as WeedHack spread. More in where to download mods safely.

2. Look at the author

An account with a history of releases, public source code and active users is a good sign. A brand-new account with one download is not. Check that the project page links to the same repository you would expect, and that the repository links back. Be cautious about a familiar mod name from an unfamiliar author.

3. Compare the file

Check that the file name, version and size roughly match the official listing. A jar that claims to be a large, well-known mod but weighs a few kilobytes is almost certainly not it. Platforms usually show a hash for each file; if you have one, compare it with the hash RatOrNot reports for your copy. If the two differ, you do not have the official file.

4. Check the mod matches the loader and version

A Fabric mod on a Forge profile will not load, so a mod that is advertised for one loader but ships metadata for another is worth a second look. Match the Minecraft version too. These are also simple signs of a sloppy re-pack.

5. Scan it

  1. Open the scanner and drop the jar in, or paste a link on the scan from a link page.
  2. Read the verdict and the listed indicators, not just the colour.
  3. If something is flagged, open the details to see which class and behaviour triggered it. See false positives for how to judge it.

What a flag usually means

The most serious findings combine a source of sensitive data with a way out:

A lone network call, some reflection or a shrunk jar is common in clean mods and usually is not a problem on its own.

6. Keep your system safe anyway

  • Never run a jar by double-clicking it unless you know what it is.
  • Keep your operating system and antivirus up to date.
  • Use two-step verification on your Microsoft and Discord accounts.
  • Install only the mods you actually need, and remove ones you no longer use.
  • Rescan after updates. A trusted mod can change when an author's account is compromised.

If you already ran something doubtful

Follow what to do if you ran an infected mod. Speed matters most for your account passwords.

A scan is a risk assessment based on static analysis. It never runs the file, and it cannot guarantee that something is safe. See how RatOrNot works for its limits.