Is upload.jar safe?
No antivirus engine flagged the JAR and sandbox returned no malicious verdict despite three MITRE techniques observed.
Zero of 75 engines detected the file. Sandbox analysis completed without a malicious verdict and no dropped children were malicious. The three MITRE techniques observed are not corroborated by any engine or sandbox verdict.
fd34bdd78452317467…4a5af3e3d591c3Recommended 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 file. Sandbox analysis completed without a malicious verdict and no dropped children were malicious. The three MITRE techniques observed are not corroborated by any engine or sandbox verdict.
The file is a 3-day-old JAR with medium prevalence. All 75 engines returned clean results, including 16 tier-1 engines. Sandbox execution produced three offensive MITRE techniques but no malicious verdict and no malicious dropped children. The single external IP contact cannot be assessed because contactedHosts is null. No external intelligence hits or similar-hash matches exist.
What We Detected
75 engines scanned the JAR; none returned a malicious or suspicious result. Sandbox execution recorded three MITRE techniques (T1055, T1543.002, T1562.001) and one direct-no complete contacted-host reputation result was available and no dropped child was flagged malicious.
Threat Behavior
The observed techniques can appear in both legitimate and malicious Java applications. Without engine detections or a malicious sandbox verdict, the evidence does not support a malware classification.
What To Do Now
Keep endpoint protection enabled. If the file originates from an untrusted source, avoid execution until additional context is available.
Where this verdict could be wrong2 caveats
- behaviour.offensiveTechniques contains T1055, T1543.002, T1562.001 — three techniques that malware commonly uses, but sandbox and engines did not corroborate malicious intent.
- contactedHosts is null — the single IP contact (162.159.36.2) cannot be assessed for reputation.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines flagged the file
- Sandbox verdict clean
- No malicious dropped children
- Three MITRE techniques observed in sandbox (T1055, T1543.002, T1562.001)
- Single external IP contact with no reputation data available
The file shows no malicious indicators across engines or sandbox; treat as safe unless new evidence emerges.
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
- 15MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 15filesystem & 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
upload.jar
fd34bdd78452317467aaff2e89377926523ade09bf96ac651c4a5af3e3d591c3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.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
3140
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3140
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>\3140
- 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\7128
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\3064
- /tmp/hsperfdata_root/3539
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- fb0ed746fdaa3c7c1f2b…cfc97fNever scannednever seen before
- 257f2c93897fec7c4fed…61bccaNever scannednever seen before
- a47808cd58b00f218df7…e61d1fNever scannednever seen before
- c1de3a9376fdaef0ba6a…308b70Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 61625fd8b084f70f242d…55abd2Never scannednever seen before
- 50c82f36208ed8040447…2d7843Never scannednever seen before
- 8e8711854186c68e2368…4a3c7cNever scannednever seen before
- 759aafcfa2395ce1b800…2af0f7Never 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
- 16sources 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 17 times from 16 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: upload.jar — fd34bdd78452317467aaff2e89377926523ade09bf96ac651c4a5af3e3d591c3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.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: 3140 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3140
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\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.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
- upload.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 310.6 KB
- Last analyzed
- Aug 19, 2026, 9:21 AM UTC
fd34bdd78452317467aaff2e89377926523ade09bf96ac651c4a5af3e3d591c3Safety & 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 upload.jar safe?
What is upload.jar?
How many antivirus engines detected upload.jar?
What is the SHA-256 hash of upload.jar?
Is it safe to open or run upload.jar?
How up to date is this analysis of upload.jar?
Community
Member reviews and reports for this exact file hash.