Darky RAT Check/Java JAR RAT Scanner

FILE SCANNER JAVA BYTECODE · RAT BEHAVIOR · CLASS FILES

Trace what a Java file is built to do.

Scan a general Java JAR or individual .class file for JVM method calls, strings, URLs, file operations, native loading, process execution and correlated RAT behavior.

01 Not executed02 Archive contents03 Evidence report

Drop a JAR or CLASS file

or click to select a file

Maximum 4 MB · Not executed · Automatically deleted

Uploads are inspected in an isolated temporary workspace and are never executed. Analysis depth depends on file size, archive complexity and available recovery engines.

CALL

Method-call map

Recovers caller classes, methods, invoked owners, descriptors and bytecode offsets.

RAT

Behavior chains

Correlates network transmission with token/file access, downloads, execution and persistence-related capabilities.

Searchable evidence

Browse recovered code maps, class inventory, strings, URLs, domains and packaged resources.

JAR

plugin.jar

Minecraft server plugin

Download full report Not executed

SCAN VERDICT

Analysis complete

0RISK

Detected package

Code recovery

Most-used external packages

JVM references

Package map

Classes by namespace

Local JAR identity

Read directly from metadata

Published-file verification

Exact hash lookup

Cryptographic fingerprints

Use these to compare exact files

Recovered metadata

plugin.yml, mod JSON/TOML and manifest

Search recovered code

This searches decompiled source and extracted text resources, not a predefined suspicious-word list.

Choose a file from the left to inspect its recovered source or JVM bytecode.

Verified JVM method invocations

These calls were parsed from compiled class bytecode.

Caller class	Caller method	Invoked owner	Invoked method

Recovered runtime strings

Strings loaded by compiled methods, with their originating class and method.

URLs

Domains

Complete archive inventory

Every readable archive entry, including classes, resources, nested JARs and embedded binaries.

Path	Type	Size	Compressed	View

Security findings

Findings require verified capabilities or behavior chains; loose words in metadata do not create critical verdicts.