File scan report
Verdict Suspicious
Is Krypton- 1. 21. 11. jar safe? Treat it as suspicious.
One major antivirus engine flagged the sample as HEUR:Trojan.Java.Generic while 15 other major antivirus engines stayed silent.
Read the whole reasonShow less
Why Suspicious? One antivirus engine (Kaspersky) flags it; nothing else confirms it.
Limited evidence
Treat as suspicious; isolate the file and await additional engine or sandbox results before any execution.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open or run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already opened or ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 65 flagged
- Flagged 1
- No detection 64
- No result 10
- Code signing Not applicable
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
1 point against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Sandbox evidence shows and techniques, yet no malicious files it created or external-intel hits were found.
The single Kaspersky detection is a meaningful signal, but the lack of major family consensus and the clean majority among other major antivirus engines prevent a definitive malicious call. Observed MITRE techniques and raise concern, yet the sandbox did not return a malicious verdict and no files it created were malicious. Medium prevalence and absence of similar-hash matches leave the file in mixed-signal territory.
What We Detected
One major antivirus engine (Kaspersky) labelled the JAR HEUR:Trojan.Java.Generic; 64 engines reported undetected.
Threat Behavior
The sample wrote several temporary files and executed icacls to modify permissions, but no malicious files it created were produced and no control-server domains were contacted. External intelligence sources returned no matches.
What To Do Now
Keep the file quarantined. Re-scan after more evidence or sandbox runs become available. Do not execute on production systems until further evidence clarifies intent.
Where this verdict could be wrong1 caveat
- Only one major antivirus engine flagged; 15 other major antivirus engines reported clean; no family consensus across engines.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 15 major antivirus engines reported clean
- No malicious files it created
- Medium prevalence across 48 submitters
- One malicious detection from a major antivirus engine
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 13sandbox rule tags
- 4spawned processes
- 0network contacts
- 11filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Hid files or windows on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Loaded extra code modules while running.
Note: Checked which security software was installed on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as downloading a file, but no download was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
Krypton-1.21.11.jar
8f9bacefa22327475476c00e00cf6ab8153707a16e9f65d5285b653a33be824d
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
javaw.exe
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
Test run - Evidence 3 of 5: ProcessSeen in the test run
cmd.exe
C:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\download.jar"" >> C:\cmdlinestart.log 2>&1
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
2620
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2620
Test run - Evidence 5 of 5: Written fileSeen in the test run
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 13 mapped techniques, every process, file, registry and network entry and 4 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 65 antivirus engines that checked it flags it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
- Kaspersky (major engine)HEUR:Trojan.Java.Generic
File fingerprint
- Last analyzed
- Aug 27, 2026, 11:38 PM UTC
- SHA-256
8f9bacefa22327475476c00e00cf6ab8153707a16e9f65d5285b653a33be824d- SHA-1
91e5af96d33707bca981eb6048f03f6eedafbefc- MD5
ae675ce43e53fe327cd05b8710eee890
About this file
Krypton-1.21.11.jar is a JAR file of 7.2 MB.
- Type and size
- JAR · 7.2 MB
- Signer
- Not applicable
- First seen
- Aug 19, 2026On VirusTotal.
- Submitted by
- 48 distinct sources
First scanned
Includes every engine result (75), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Krypton-1.21.11.jar safe, or is it malware?
What is Krypton-1.21.11.jar?
How many antivirus engines detected Krypton-1.21.11.jar?
What should I do if I already opened or ran Krypton-1.21.11.jar?
What is the SHA-256 hash of Krypton-1.21.11.jar?
How up to date is this analysis of Krypton-1.21.11.jar?
Community
Member reviews and reports for this exact file hash.