File scan report
Verdict Safe
Is nora-
Only MaxSecure flagged this JAR with a generic label, while all 17 major antivirus engines and the completed sandbox provided no malware verdict.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the project's own website.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 66 flagged
- Flagged 1
- No detection 65
- No result 9
- Code signing Not applicable
- Test run Completed
- First seen 6mo ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The lone detection comes from MaxSecure, a less reliable engine, and uses a generic label rather than identifying a malware family. All 17 major antivirus engines remained silent, and one completed sandbox issued no malicious verdict, although two offensive techniques and six unresolved files it created justify keeping security software enabled.
Only 1 of the 66 antivirus engines that checked it flagged the JAR, and that result came from MaxSecure with a generic Trojan label. All 17 major antivirus engines, including Microsoft, Kaspersky, ESET-NOD32, and BitDefender, reported no detection. One sandbox observed techniques and but did not issue a malicious verdict, record persistence indicators, or observe network contacts. Six dropped files were inspected without a malicious result, though their individual status remains unresolved. Researcher-curated intelligence produced no corroborating family or YARA match, making a false positive substantially more likely than an active Trojan.
What We Detected
MaxSecure was the only engine to flag the file, producing the generic label “Trojan.Malware.300983.susgen.” The remaining antivirus evidence included no major detections or named-family consensus; all 17 major antivirus engines reported no detection.
Threat Behavior
One completed sandbox mapped activity to T1543.002 and T1562.001, but it issued no malicious verdict and recorded no persistence indicators or network contacts. Six written files it created were inspected without a malicious child finding, although each child remains unresolved. No complete contacted-host reputation result is available because contactedHosts was not saved.
What To Do Now
Keep security software enabled and obtain the JAR from the project's official release channel. If its source or integrity cannot be verified, test it in an isolated environment before using it with valuable game data or credentials.
Where this verdict could be wrong4 caveats
- MaxSecure flagged the sample with the generic label 'Trojan.Malware.300983.susgen'.
- The completed sandbox mapped activity to offensive techniques and T1562.001, which warrants caution even though it issued no malicious verdict.
- All 6 inspected files it created have unknown verdicts, so their absence from the malicious rollup is not definitive.
- No contacted-host reputation result was saved, meaning no complete host-reputation cross-check is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- All 17 major antivirus engines reported no detection.
- Only 1/66 engines flagged the sample, and it was less reliable.
- No malicious sandbox verdict was issued.
- No named malware-family consensus or external-intelligence hit exists.
- No dropped file is known to be malicious.
- MaxSecure produced one generic Trojan detection.
- Sandbox activity included and T1562.001.
- No complete contacted-host reputation check is available.
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- 11sandbox rule tags
- 4spawned processes
- 0network contacts
- 12filesystem & mutex artifacts
Includes 11 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 66 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
The saved verdict treats these detections as likely false positives.
- MaxSecureTrojan.Malware.300983.susgen
File fingerprint
- Last analyzed
- Sep 8, 2026, 3:43 PM UTC
- SHA-256
ae09601865e8338b23a72df28ed897676a48a0949d125f8f1ac7acad6b7a53d4- SHA-1
2cacb240c76b25bdbb7d89f168b74d634f5f3527- MD5
8f47ca03f175b525d97a2d1a8ac108a9
About this file
nora-tweaks-1.21.11-build-8.jar is a JAR file of 2.2 MB.
- Type and size
- JAR · 2.2 MB
- Signer
- Not applicable
- First seen
- Apr 28, 2026On VirusTotal.
- Submitted by
- 85 distinct sources
First scanned
Includes every engine result (75) 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 nora-tweaks-1.21.11-build-8.jar safe?
What is nora-tweaks-1.21.11-build-8.jar?
How many antivirus engines detected nora-tweaks-1.21.11-build-8.jar?
What is the SHA-256 hash of nora-tweaks-1.21.11-build-8.jar?
Is it safe to open or run nora-tweaks-1.21.11-build-8.jar?
How up to date is this analysis of nora-tweaks-1.21.11-build-8.jar?
Community
Member reviews and reports for this exact file hash.