Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/analyzing-java-jar-malwareMalware and ransomware analysis

analyzing-java-jar-malware

⁨Analyzes Java/JAR malware (such as Adwind/jRAT-class cross-platform RATs) by⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/analyzing-java-jar-malware

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
5DVNjGRIpX…5yJ3X1BA==The CLI checks the SHA-256 and the signature before it writes a file.
Package71bdbb43…4e43d6f2
71bdbb43d240…090b4e43d6f24 files · ⁦3.6 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-java-jar-malware@da7600a

When to Use

  • You have a malicious or suspicious .jar (often a cross-platform RAT) and need to map its structure, entry point, obfuscation, and capability surface before decompiling.
  • You want to triage a Java payload without running the JVM.

Do not use java -jar to run it — that executes the malware. Treat the JAR as a ZIP and read its contents statically.

Prerequisites

  • The JAR file, read inertly. Optional: a Java decompiler (CFR, Procyon) for the next stage.

Safety & Handling

  • Read the archive statically; never launch the JVM on the sample. Defang any URLs found.

Workflow

Step 1: Inventory the archive and entry point

bash
python scripts/analyst.py inspect sample.jar

Lists .class files, embedded resources/payloads (nested JARs, scripts, encrypted blobs), and reads META-INF/MANIFEST.MF for Main-Class/Premain-Class.

Step 2: Detect obfuscation and packers

Flags obfuscator fingerprints (Allatori, ProGuard, Zelix), single-character class/package names, and string-decryption indicators.

Step 3: Flag capability classes

Surface dangerous API usage in strings/constant pools: Runtime.exec/ProcessBuilder, java.lang.reflect, URLClassLoader, javax.crypto, java.net.Socket, registry/persistence helpers.

Step 4: Route to decompilation

Hand the key classes to a decompiler (CFR/Procyon) for source recovery; record IOCs.

Validation

  • The manifest entry point is read and reported.
  • Embedded payloads/nested archives are enumerated.
  • Capability flags are backed by concrete class/string evidence.

Pitfalls

  • String-encrypted samples where capability strings appear only after decryption.
  • Multi-stage droppers that unpack a second JAR at runtime.
  • Benign obfuscated commercial JARs — corroborate with capability and delivery context.

References

  • See references/api-reference.md for the inspector.
  • JVM/JAR format and ATT&CK T1027 references (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesYesYes
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a71bdbb43Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login