RatOrNot
All detections

Detection

Evasion techniques in malicious Minecraft mods

Last updated November 16, 2026

Evasion code does not steal anything itself. It tries to make sure nobody notices the stealing: by stopping when it is being watched, waiting before it acts, or removing itself afterwards.

Rules in this family

  • evade.debugger-check: looks for debug arguments such as a debug agent.
  • evade.vm-check: looks for virtual-machine or sandbox hints.
  • evade.sandbox-user: checks the user or machine name against known sandbox names.
  • evade.analysis-tools: looks for analysis tool processes.
  • evade.delayed-network: waits a long time before using the network.
  • evade.self-delete: deletes its own file.
  • evade.security-manager: installs or replaces a security manager.
  • exec.attach-api: uses the attach API.
  • exec.instrumentation: uses instrumentation to change loaded classes.

A single check can be innocent: some mods read JVM arguments to adapt to settings. Together with network use or a loader, it matters much more.

Related reading

How malicious mods hide.

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.