File scan report
Verdict Safe
Is max-
Zero of the 55 antivirus engines that checked it detected the sample.
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
The file can be considered safe for normal use; continue monitoring any outbound connections if executed.
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 55 flagged
- Flagged 0
- No detection 55
- No result 20
- Code signing Not applicable
- Test run Completed
- First seen 5mo ago
Chapter 02
Why we think so
0 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The complete absence of detections across 75 engines, including 17 major antivirus engines, outweighs the two observed MITRE techniques. Medium prevalence over 112 days and a clean community annotation further support a benign classification. No dropped malicious files it created or external-intel hits exist to contradict the clean engine consensus.
What We Detected
75 engines scanned the 30 760-byte JAR; none returned a malicious or suspicious result. Four files it created were created, none flagged malicious.
Threat Behavior
The observed techniques can appear in both legitimate research tools and malware. No engine family consensus, no external-intel corroboration, and no malicious child artifacts were found. Medium prevalence suggests the file is not rare or brand-new.
What To Do Now
Keep security software enabled. If the JAR is required, run it only in an isolated test environment and monitor for unexpected outbound traffic.
Where this verdict could be wrong1 caveat
- Sandbox observed and T1562.001, but the malicious-sandbox-verdict flag remains false and no engine labelled the sample malicious.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 75 engines
- No malicious files it created
- Medium prevalence over 112 days
- Community annotation labels file clean
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
Includes 13 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 55 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
- Aug 31, 2026, 2:53 AM UTC
- SHA-256
a0ac37df32fbfbfad3b7c9dede001b7f175a03f0ce0569b583c566840bc884d6- SHA-1
4e0c60e6004c9fed40b13bbc883c05de14cf0c17- MD5
7046a525829ea3e4217dcd2e1eb206ec
About this file
max-bypass.jar is a JAR file of 30.8 kB.
- Type and size
- JAR · 30.8 kB
- Signer
- Not applicable
- First seen
- May 10, 2026On VirusTotal.
- Submitted by
- 46 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 max-bypass.jar safe?
What is max-bypass.jar?
How many antivirus engines detected max-bypass.jar?
What is the SHA-256 hash of max-bypass.jar?
Is it safe to open or run max-bypass.jar?
How up to date is this analysis of max-bypass.jar?
Community
Member reviews and reports for this exact file hash.