File scan report
Verdict Safe
Is cheatutils- 3. 15. 0- forge- 1. 21. 11. jar safe? Yes, no threats found.
None of the 65 antivirus engines that checked it flagged this widely submitted JAR, and its completed sandbox run produced no malicious verdict despite two cautionary technique…
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
Use it only from the expected mod source and verify the SHA-256 before installation. Keep antivirus protection enabled and avoid unnecessary administrator privileges.
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
0 of 65 flagged
- Flagged 0
- No detection 65
- No result 8
- Code signing Not applicable
- Test run Completed
- First seen 9mo 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
None of the 65 antivirus engines that checked it flagged the file, including 16 major antivirus engines, and it has appeared across 284 sources.
The strongest evidence is broad antivirus silence: none of the 65 antivirus engines that checked it flagged the JAR, including all 16 major antivirus engines that reported. The file is also well established, with 304 submissions from 284 sources, reducing concern that it is an unrecognized new sample. One completed sandbox run returned clean and recorded no sample network contacts, persistence indicators, injection targets, or registry changes. However, the runtime mapping includes and T1543.002, so the behavioral picture is not entirely uneventful. No malware-specific research rules or repository match corroborated those mappings, and no file it created has a saved malicious verdict.
What We Detected
None of the 65 antivirus engines that checked it flagged the JAR, including 16 major antivirus engines such as BitDefender, ESET, Kaspersky, Microsoft, and Fortinet. The file is established across 284 sources and 304 submissions, and no malware-specific research rule or malware-repository match was found.
Threat Behavior
One completed sandbox run returned clean and recorded no sample network contacts, process injection, persistence indicators, or registry changes. It did map T1562.001 and T1543.002, which are associated with defense impairment and systemd service activity, but the supplied process details include Java execution and Linux log-rotation activity rather than confirmed hostile actions. Five dropped files remain unclassified, and no complete contacted-host reputation result is available.
What To Do Now
Use the JAR only if it came from the expected project or mod distribution channel, and keep security software enabled. Back up the relevant game profile before installation and avoid granting unnecessary elevated privileges.
Where this verdict could be wrong3 caveats
- The runtime mapping includes T1562.001, associated with impairing defenses, and T1543.002, associated with systemd service activity; these mappings warrant caution despite the clean sandbox result.
- Five dropped files lack saved verdicts, so their contents remain unclassified.
- A complete reputation check was not available for contacted hosts, although the observed run recorded no sample network contacts.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 65 antivirus engines that checked it flagged the file.
- All 16 reporting major antivirus engines returned no detection.
- The file has been submitted 304 times from 284 distinct sources.
- The completed sandbox run returned clean and showed no sample network contacts.
- No malware-specific research rules or malware-repository match were found.
- The test run mapped techniques associated with impairing defenses and systemd service activity.
- Five files created or extracted during analysis do not have saved classifications.
- No complete reputation cross-check is available for contacted hosts.
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- 7sandbox rule tags
- 4spawned processes
- 0network contacts
- 13filesystem & mutex artifacts
Includes the sandbox verdicts, 7 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 65 antivirus engines that checked it flag 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.
File fingerprint
- Last analyzed
- Oct 10, 2026, 11:01 PM UTC
- SHA-256
e3346009b5570a9588854cd11176c7ea0483e353e8f731262084fe89684e19bd- SHA-1
bbcb2c58c6b0a0135d4f0ec6457b8f2f737b2f7c- MD5
6bf334e5c2a4c622bfdd49fec99cbf46
About this file
cheatutils-3.15.0-forge-1.21.11.jar is a JAR file of 2.5 MB.
- Type and size
- JAR · 2.5 MB
- Signer
- Not applicable
- First seen
- Jan 28, 2026On VirusTotal.
- Submitted by
- 284 distinct sources
First scanned
Includes every engine result (73) 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 cheatutils-3.15.0-forge-1.21.11.jar safe?
What is cheatutils-3.15.0-forge-1.21.11.jar?
How many antivirus engines detected cheatutils-3.15.0-forge-1.21.11.jar?
What is the SHA-256 hash of cheatutils-3.15.0-forge-1.21.11.jar?
Is it safe to open or run cheatutils-3.15.0-forge-1.21.11.jar?
How up to date is this analysis of cheatutils-3.15.0-forge-1.21.11.jar?
Community
Member reviews and reports for this exact file hash.