Is opsec-1.21.2-1.21.5+v1.1.7.1.jar safe?
No antivirus engine detected this JAR, while isolated runtime mappings and one unchecked direct-IP contact justify retaining normal endpoint protections and source verification.
None of 75 antivirus engines flagged the JAR, including 13 tier-1 engines that completed detection checks, and the sandbox issued no malicious conclusion. Runtime evidence nevertheless mapped activity to T1055 and T1562.001 and recorded one direct-IP connection whose reputation was not completely checked, so use only a trusted distribution source.
ea83031c356d47bfaf…642583ce7a7434Recommended 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 the JAR, including 13 tier-1 engines that completed detection checks, and the sandbox issued no malicious conclusion. Runtime evidence nevertheless mapped activity to T1055 and T1562.001 and recorded one direct-IP connection whose reputation was not completely checked, so use only a trusted distribution source.
The strongest evidence is broad detection silence: 0 of 75 engines flagged the file, with BitDefender, Kaspersky, ESET-NOD32, Microsoft, and Fortinet among those reporting no detection. One completed sandbox run produced no malicious verdict, and four inspected child hashes produced no confirmed malicious child. However, the runtime mapping includes T1055 and T1562.001, which are meaningful offensive-behavior indicators even though the recorded evidence does not establish intent or a specific injection method. The sample also contacted 162.159.36.2 directly, and no complete host-reputation result is available because the contacted-host check was not saved. With moderate circulation, no family consensus, and no YARAify, CIRCL, or MalwareBazaar corroboration, the overall evidence favors benign software while preserving some caution around runtime behavior.
What We Detected
No antivirus engine flagged the JAR: 0 of 75 reported it as malicious or suspicious. Thirteen tier-1 engines completed checks without a detection, including BitDefender, Kaspersky, ESET-NOD32, Microsoft, and Fortinet. No engine family consensus or researcher-curated intelligence match identified a known threat.
Threat Behavior
One sandbox run mapped activity to T1055 and T1562.001, associated with process injection and impairment of defenses. These mappings deserve caution, but the saved evidence does not prove a particular injection method, and the sandbox did not issue a malicious verdict. The file also contacted 162.159.36.2 directly; because the contacted-host reputation check is unavailable, that connection cannot be characterized as benign or malicious. Four child files were inspected without a confirmed malicious result, although their individual verdicts remain unknown.
What To Do Now
Confirm that the hash and filename match the project's official release channel before running the JAR. Keep antivirus and endpoint protection enabled, and avoid granting unnecessary privileges or network access if the source cannot be verified.
Where this verdict could be wrong3 caveats
- The runtime mapping includes T1055 process injection and T1562.001 defense impairment, both offensive techniques that warrant caution despite the absence of engine detections.
- The sample contacted 162.159.36.2 directly, but contactedHosts=null means the IP's reputation was not completely checked or saved.
- All four inspected dropped children have unknown individual verdicts, so droppedChildren.hasMaliciousChild=false does not establish that those files are benign.
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 reported malicious or suspicious findings.
- tier1Malicious=0 and 13 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false.
- Runtime evidence maps activity to MITRE T1055.
- Runtime evidence maps activity to MITRE T1562.001.
- Direct connection to 162.159.36.2 lacks a completed host-reputation result.
- Four dropped child hashes have unknown individual verdicts.
Use the JAR only if its hash matches an official release from the expected project. Keep endpoint protection enabled and investigate unexpected network access or requests for elevated privileges.
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
- 14MITRE 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
opsec-1.21.2-1.21.5+v1.1.7.1.jar
ea83031c356d47bfafd1928f42a6c5d6232a2a25954a4d2e18642583ce7a7434
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
3300
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3300
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>\3300
- 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\1432
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\4760
- /tmp/hsperfdata_root/3570
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 6260a9b1123d502b3470…78b306Never scannednever seen before
- 29db8f436a123aaa6368…477461Never scannednever seen before
- f23b4c4f8ddf1cf7d4d3…3bc549Never 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
- 117sources 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 127 times from 117 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: opsec-1.21.2-1.21.5+v1.1.7.1.jar — ea83031c356d47bfafd1928f42a6c5d6232a2a25954a4d2e18642583ce7a7434
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: 3300 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3300
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
- opsec-1.21.2-1.21.5+v1.1.7.1.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 479.9 KB
- Last analyzed
- Sep 14, 2026, 1:46 PM UTC
ea83031c356d47bfafd1928f42a6c5d6232a2a25954a4d2e18642583ce7a7434Safety & 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 opsec-1.21.2-1.21.5+v1.1.7.1.jar safe?
What is opsec-1.21.2-1.21.5+v1.1.7.1.jar?
How many antivirus engines detected opsec-1.21.2-1.21.5+v1.1.7.1.jar?
What is the SHA-256 hash of opsec-1.21.2-1.21.5+v1.1.7.1.jar?
Is it safe to open or run opsec-1.21.2-1.21.5+v1.1.7.1.jar?
How up to date is this analysis of opsec-1.21.2-1.21.5+v1.1.7.1.jar?
Community
Member reviews and reports for this exact file hash.