Is upload.jar safe?
No antivirus engine detected the JAR, and runtime checks found no confirmed malware, although three offensive-technique mappings justify retaining normal endpoint protection.
None of 75 antivirus engines flagged this JAR, including the reporting tier-1 engines, and the completed sandbox produced no malicious verdict. Three offensive MITRE mappings, including T1055, remain cautionary signals, but they lack corroboration from engine detections, malicious children, researcher rules, or fully adverse network reputation.
eb79b9876332010733…e2a0fb449f6cf2Recommended 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.
None of 75 antivirus engines flagged this JAR, including the reporting tier-1 engines, and the completed sandbox produced no malicious verdict. Three offensive MITRE mappings, including T1055, remain cautionary signals, but they lack corroboration from engine detections, malicious children, researcher rules, or fully adverse network reputation.
The strongest evidence is the complete absence of detections across 75 antivirus engines, with 15 tier-1 engines reporting no detection. One completed sandbox did not produce a malicious verdict, and none of nine inspected dropped files was identified as malware, although their individual verdicts remain unknown. Runtime mappings to T1055, T1543.002, and T1562.001 are meaningful counter-signals, but technique mappings alone do not establish intent or confirm process injection. The two contacted domains were not present in the malicious or suspicious host cache, while the observed IP lacked a documented reputation check, so network coverage is incomplete. No YARAify rules or MalwareBazaar record corroborate malware, and 321 sources submitted the file 345 times within four days. Overall, the offensive mappings warrant caution but are outweighed by broad engine silence and the absence of confirmed malicious runtime outcomes.
What We Detected
The JAR received 0 detections from 75 antivirus engines, with engines.tier1Malicious=0 and 15 tier-1 engines reporting no detection. No malware family was identified, YARAify returned zero matching rules, and no MalwareBazaar record was present. The file was submitted 345 times by 321 sources during its first four days, indicating substantial recent distribution.
Threat Behavior
One completed sandbox mapped activity to T1055, T1543.002, and T1562.001, including possible process injection and defense impairment. These mappings are cautionary, but the sandbox itself produced no malicious verdict, no persistence indicators were recorded, and none of nine inspected dropped files was identified as malware; all nine child verdicts remain unknown. The reputation check covered both observed domains without finding malicious or suspicious records, but the additional observed IP was not documented as inspected, so network reputation coverage was incomplete.
What To Do Now
Use the file only if it came from the expected source and its purpose is understood. Keep antivirus and endpoint protection enabled, and avoid granting elevated privileges unless the application clearly requires them.
Where this verdict could be wrong3 caveats
- MalwareTips.Synth.ProcessInjection fired at high severity and maps the saved activity to T1055, which warrants caution despite the absence of antivirus detections.
- T1543.002 and T1562.001 are additional offensive-technique mappings, but the sole completed sandbox did not issue a malicious verdict.
- All nine dropped-child verdicts are unknown, and the observed IP 162.159.36.2 lacks a documented host-reputation result.
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 antivirus engines reported malicious or suspicious results.
- engines.tier1Malicious=0 and engines.tier1ReportedClean=15.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false.
- Runtime evidence maps activity to T1055, T1543.002, and T1562.001.
- MalwareTips.Synth.ProcessInjection fired with high severity.
- The file is only four days old.
- All nine dropped children have unknown individual verdicts.
- Host-reputation coverage did not document inspection of the observed IP 162.159.36.2.
Proceed only when the JAR came from a trusted, expected source, and keep endpoint protection enabled. If its origin is uncertain, run it in an isolated environment rather than granting administrative access.
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
Partial2 of 3 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule 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
- 16MITRE ATT&CK techniques
- 15spawned processes
- 3network contacts
- 15filesystem & mutex artifacts
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.
- atm.teams.mira.tm.svc.cloud.microsoft
- assets.msn.com
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2840
- 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\6788
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\5944
- /tmp/hsperfdata_root/3542
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- 5838c640563b1450d0c9…6c50daNever scannednever seen before
- 9928d81106da51588bcb…1a516fNever scannednever seen before
- 1d35f6bc8b2faddac5c0…3b9a0cNever scannednever seen before
- b468bf508c1b034631c5…457d6eNever 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.
- 1rule hit recorded
- 0 / 75engines flagged
- 321sources 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 345 times from 321 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: upload.jar — eb79b9876332010733a8e0d7ce4fe0377846059a9e28859029e2a0fb449f6cf2
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: 2840 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2840
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: atm.teams.mira.tm.svc.cloud.microsoft — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: assets.msn.com — 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"
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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- upload.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 12.6 MB
- Last analyzed
- Oct 7, 2026, 4:56 PM UTC
eb79b9876332010733a8e0d7ce4fe0377846059a9e28859029e2a0fb449f6cf2Safety & 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.