Drop the mod.
Pick a .jar from your device. No account, no upload, no running unknown code.
That new mod could do more than you think.
Look inside the .jar before it gets inside your PC.
A LOOK UNDER THE HOOD
Mods should change your game.
Not take over your machine.
Pick a .jar from your device. No account, no upload, no running unknown code.
We unpack the archive and inspect class references for sensitive capabilities and suspicious strings.
Get the class, the matched reference, and the reason it matters. Make an informed call before you play.
NO BLACK BOX. JUST EVIDENCE.
3 sensitive code references found in this example.
A reference is a lead, not a verdict. Static analysis can miss hidden behavior and cannot certify that a mod is safe.
LOCAL MEANS LOCAL.
The scan happens in your browser. Your .jar isn’t sent to a server, saved to a cloud, or executed. Close the tab and the scan is gone.
Inspect your first modBEFORE YOU DROP IN
This browser version reads UTF-8 constants in Java class files and looks for references to process execution, network connections, credential locations, native code, and dynamic loading. It shows the matching class and evidence. It does not decompile source code or verify named RAT families.
No. A scan with no matched indicators is not a safety guarantee. Obfuscation, encrypted strings, native libraries, and nested archives can hide behavior. Download mods from sources you trust and use the report as one additional check.
Never. AntiRat reads the archive as data and inspects its bytecode references. It does not launch Java or execute any code from your .jar.
Java Edition mods distributed as .jar files, including Fabric, Forge, and NeoForge, up to 25 MB. Archives that exceed inspection limits are reported as incomplete. Nested archives and native binaries are identified but not inspected.