Is max-bypass.jar safe?
No antivirus engine flagged the JAR despite sandbox observation of process-injection techniques.
Zero of 75 engines detected the sample. Sandbox recorded T1055 and T1562.001 activity plus a direct-IP connection, yet returned no malicious verdict and dropped no malicious children.
a0ac37df32fbfbfad3…c566840bc884d6Recommended next actions
Before opening or running
Open or run it only when its publisher and download source have been independently verified.
If you already opened or ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Zero of 75 engines detected the sample. Sandbox recorded T1055 and T1562.001 activity plus a direct-IP connection, yet returned no malicious verdict and dropped no malicious children.
The complete absence of detections across 75 engines, including 17 tier-1 engines, outweighs the two observed MITRE techniques. Medium prevalence over 112 days and a clean community annotation further support a benign classification. The direct-IP contact lacks domain context and host-reputation data, so it remains inconclusive. No dropped malicious children 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. Sandbox execution logged MITRE techniques T1055 (process injection) and T1562.001 (defense evasion) plus a single direct-IP connection to 162.159.36.2. Four child files 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 endpoint protection 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 MITRE T1055 and T1562.001, but hasMaliciousSandboxVerdict 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 dropped children
- Medium prevalence over 112 days
- Community annotation labels file clean
- Sandbox recorded process-injection and defense-evasion techniques
The file can be considered safe for normal use; continue monitoring any outbound connections if executed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 13MITRE ATT&CK techniques
- 6spawned processes
- 1network contacts
- 11filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
max-bypass.jar
a0ac37df32fbfbfad3b7c9dede001b7f175a03f0ce0569b583c566840bc884d6
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\download.jar"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
5992
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5992
04Isolated runtime analysis - Written fileObserved
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5992
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp
- C:\Users\user\AppData\Local\Temp\hsperfdata_user
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\6948
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\4308
- /tmp/hsperfdata_root/3006
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 3b435f43f0e7f61f86e0…507015Never scannednever seen before
- c4c35b696b1d2c9da02f…2adf25Never scannednever seen before
- c1de3a9376fdaef0ba6a…308b70Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 75engines flagged
- 46sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 52 times from 46 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: max-bypass.jar — a0ac37df32fbfbfad3b7c9dede001b7f175a03f0ce0569b583c566840bc884d6
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\download.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 5992 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5992
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\download.jar"The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- max-bypass.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 30.0 KB
- Last analyzed
- Aug 31, 2026, 2:53 AM UTC
a0ac37df32fbfbfad3b7c9dede001b7f175a03f0ce0569b583c566840bc884d6Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open or run it only when its publisher and download source have been independently verified.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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.