MalwareTipsTools

File scan report

Verdict Safe

Analyzed , 5 hours ago

Is opsec-26.3+v1.1.7.4.jar safe? Yes, no threats found.

None of the 60 antivirus engines that checked it flagged this Java archive, sandbox runs came back clean, and reference databases and contacted hosts show nothing hostile.

Moderate evidence · No engine flags it; this type of file has no publisher signature to check.

Open or run it as usual if it came from the official source

Low risk based on current evidence. Run it only if you trust its source, and keep your antivirus protection enabled.

Good practice2 tips

We found nothing harmful in this file.

  1. Run it only if it came from the project's own website.

  2. Keep your security software and system updates switched on.

No scanner can promise a file is 100% safe.

Antivirus results

0 of 60 flagged

  • Flagged 0
  • No detection 60
  • No result 15
Fileopsec-26.3+v1.1.7.4.jar485.6 kBSHA-256 ca06658887d3…f6831f
  • Code signing Not applicable
  • Test run Completed
  • First seen 1mo ago
When we scanned it, 68 sources had submitted it to VirusTotal (75 submissions).

Chapter 02

Why we think so

1 point against it and 4 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The combined sandbox verdict was clean and no injection target was recorded. No reference database lists it as malicious.

Full reasoning

None of the 60 antivirus engines that checked it flagged the file, and 60 engines reported results, which is adequate coverage. The only hosts contacted are background traffic from the analysis machine, and our host cross-check found nothing malicious. MalwareBazaar, CIRCL and YARAify have no hits, and 68 different sources have submitted the file. Nobody inspected the archive's inner contents, which limits certainty.

Detailed assessment

What we detected

No engine flagged this JAR file, and the major antivirus engines (BitDefender, Kaspersky, ESET-NOD32, Microsoft) returned clean. Reference databases have no entry marking it as malicious.

Threat behavior

In four sandbox runs the file launched the Java runtime as expected. Only the analysis machine's own background traffic was recorded, and the two dropped files have no saved verdict, which is neutral.

What to do now

Treat it like any Java program from an unverified source: run it only if you trust where it came from, since its contents were not inspected directly.
Where this verdict could be wrong2 caveats
  • Sandbox MITRE mappings and were recorded, but without any injected process or defence-tampering artefact, so they are weak.
  • Nobody inspected the archive's contents and no signature or GitHub release match exists, so there is no strong positive proof of legitimacy.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Points in its favour
  • No engine flagged it, including 14 major antivirus engines
  • Clean combined sandbox verdict across four runs
  • No hits in MalwareBazaar, CIRCL or YARAify
  • Submitted by 68 different sources
Points against
  • The archive's inner contents were not inspected directly, so hidden logic cannot be fully excluded.

6 sources checked · all complete. See every source

Chapter 03

What it did in our test

It ran in 4 isolated tests; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 4isolated sandbox runs
  • 16sandbox rule tags
  • 4spawned processes
  • 0network contacts
  • 13filesystem & mutex artifacts

Runtime behaviour

What this file did when executed

This file was detonated in 4 sandboxes and its runtime behaviour was observed.

1 clean detonation

Sandbox verdicts

1
  • VT: CLEANClean

Techniques observed in the sandbox

16

MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.

  • T1027· Obfuscated code
  • T1055· Process injection
  • T1059· Runs commands
  • T1064
  • T1074
  • T1082· System recon
  • T1105· Network file transfer
  • T1106
  • T1129· Loads modules
  • T1202
  • T1518.001· Checks your AV
  • T1543.002· Service install
  • T1562.001· Disables security
  • T1564· Hides artifacts
  • T1564.001· Hides artifacts
  • T1564.003· Hides artifacts

Observed activity

Processes started
4

Programs the file ran, with their command lines.

  • javaw.exe"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.jar"
  • cmd.exeC:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\runtime.jar"" >> C:\cmdlinestart.log 2>&1
  • java.exe"C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\runtime.jar"
  • java/usr/bin/java -jar /tmp/download.jar
Files
13

Files the file created, changed or deleted.

  • WrittenC:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2956
  • WrittenC:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
  • WrittenC:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp
  • WrittenC:\Users\user\AppData\Local\Temp\hsperfdata_user
  • WrittenC:\Users\user\AppData\Local\Temp\hsperfdata_user\6796
  • WrittenC:\cmdlinestart.log
Show all 13 entries for files
  • Written\Device\ConDrv\\Connect
  • Written/proc/3541/coredump_filter
  • Written/tmp/hsperfdata_root/3541
  • Written/var/log/auth.log.1.gz
  • Written/var/log/kern.log.1.gz
  • DeletedC:\Users\user\AppData\Local\Temp\hsperfdata_user\1404
  • Deleted/tmp/hsperfdata_root/3541
Sandbox background — not the file
13

The analysis machine's own processes and connections, recorded in every run.

  • VM processicacls.exeC:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
  • VM processconhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1
  • VM processsh/bin/sh sh -c "\n\t\tinvoke-rc.d --quiet cups restart > /dev/null\n" logrotate_script "/var/log/cups/*log "
  • VM processinvoke-rc.d/usr/sbin/invoke-rc.d invoke-rc.d --quiet cups restart
  • VM processrunlevel/sbin/runlevel
  • VM processsystemctl/usr/bin/systemctl systemctl --quiet is-enabled cups.service
Show all 13 entries for sandbox background — not the file
  • VM processls/usr/bin/ls ls /etc/rc[S2345].d/S[0-9][0-9]cups
  • VM processsystemctl/usr/bin/systemctl systemctl --quiet is-active cups.service
  • VM processgzip/bin/gzip
  • VM processsh/bin/sh sh -c /usr/lib/rsyslog/rsyslog-rotate logrotate_script /var/log/syslog
  • VM processrsyslog-rotate/usr/lib/rsyslog/rsyslog-rotate
  • VM hostcl-glcb907925.gcdn.co
  • VM hostnexusrules.officeapps.live.com

Dropped payload

Files this sample writes at runtime

This file drops 2 children at runtime. None are currently flagged malicious in our cache. 2 have no saved verdict and were not checked; that is missing coverage, not a finding.

2 not checked
  • 8602b1002c6fd77ae63a…91bf1cNot checked
    no saved verdict
  • e02906102248db21e6f5…537c03Not checked
    no saved verdict

Chapter 04

Technical details

None of the 60 antivirus engines that checked it flag it.

Sources checked

Every check behind this verdict

6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompletePositive signal: 0 of 60 engines flagged it · 15 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPE Sandbox, ZenboxComplete4 runs: 1 clean, 3 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete2 contacted hosts checked
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

File fingerprint

Last analyzed
Nov 17, 2026, 9:46 PM UTC
SHA-256
ca06658887d3fe61f4a35f6062f7e6e7ccacefcb4f3a60b20d288e5e5cf6831f
SHA-1
4e4be64ec4ca49a9a129a5624e0b53a6812cd607
MD5
3caecdbb19621c121e51b0d1f1324c71

About this file

opsec-26.3+v1.1.7.4.jar is a JAR file of 485.6 kB.

Type and size
JAR · 485.6 kB
Signer
Not applicable
First seen
Sep 24, 2026On VirusTotal.
Submitted by
68 distinct sources

First scanned

Antivirus consensus

0 of 60 engines flagged this file

0 malicious0 suspicious60 not flagged15 no result

15 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.

  • Tier-114 engines
    0flagged
  • Tier-233 engines
    0flagged
  • Low-trust13 engines
    0flagged
No antivirus engine flagged this file.
View all 75 engine results
  • AcronisClean
  • AhnLab-V3Clean
  • AlibabaClean
  • alibabacloudClean
  • ALYacClean
  • Antiy-AVLClean
  • APEXNo result
  • ArcabitClean
  • AvastNo result
  • Avast-MobileClean
  • AVGNo result
  • AviraClean
  • BitDefenderClean
  • BitDefenderFalxNo result
  • BkavClean
  • CAT-QuickHealClean
  • ClamAVClean
  • CMCClean
  • CrowdStrikeClean
  • CTXClean
  • CylanceNo result
  • CynetClean
  • DeepInstinctNo result
  • DrWebClean
  • ElasticNo result
  • EmsisoftClean
  • ESET-NOD32Clean
  • F-SecureClean
  • FortinetClean
  • GDataClean
  • GoogleClean
  • GridinsoftClean
  • huorongClean
  • IkarusClean
  • JiangminClean
  • K7AntiVirusClean
  • K7GWClean
  • KasperskyClean
  • KingsoftClean
  • LionicClean
  • MalwarebytesClean
  • MaxSecureClean
  • McAfeeDClean
  • MicrosoftClean
  • MicroWorld-eScanClean
  • NANO-AntivirusClean
  • PaloaltoNo result
  • PandaClean
  • RisingClean
  • SangforClean
  • SentinelOneClean
  • SkyhighNo result
  • SophosClean
  • SUPERAntiSpywareClean
  • SymantecClean
  • SymantecMobileInsightNo result
  • TACHYONClean
  • tehtrisNo result
  • TencentClean
  • TrapmineNo result
  • TrellixENSNo result
  • TrendMicroNo result
  • TrendMicro-HouseCallClean
  • TrustlookClean
  • VaristClean
  • VBA32Clean
  • VIPREClean
  • VirITClean
  • ViRobotClean
  • WebrootClean
  • XcitiumClean
  • YandexClean
  • ZillyaNo result
  • ZoneAlarmClean
  • ZonerClean

Rule-based evidence

Signatures and behavior heuristics

Low-severity pattern matches — worth noting but not on their own cause for alarm.

1 heuristic
MITRE ATT&CK profile
Defense evasion× 1
Behavior heuristics
Deterministic patterns derived from scan data and observed runtime behavior
  • ProcessInjectionlow

    VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.

    Evidence

    T1055 (sandbox MITRE mapping)

Prevalence

How widely this file has been seen

Moderate prevalence — neither rare nor common. No strong prior applies.

Medium
Unique uploaders
68
Moderate upload volume.
Total submissions
75
Includes repeat uploads by the same source.
First seen
2mo ago
Sep 24, 2026
Prevalence quadrant
Rare · New
Needs evidence-led scrutiny
Common · New
Just-released software
Rare · Old
Niche or internal tooling
Common · Old
Often established software

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is opsec-26.3+v1.1.7.4.jar safe?
We found nothing harmful in opsec-26.3+v1.1.7.4.jar. None of the 60 antivirus engines that checked it flag it. Run it only if it came from the project's own website.
What is opsec-26.3+v1.1.7.4.jar?
opsec-26.3+v1.1.7.4.jar is a Java program (JAR), about 485.6 kB. VirusTotal first saw it on Sep 24, 2026.
How many antivirus engines detected opsec-26.3+v1.1.7.4.jar?
None of the 60 antivirus engines that checked it flag opsec-26.3+v1.1.7.4.jar. That is a good sign, but not proof, so we also weigh who made it, how widely it is used and what it did in a test run.
What is the SHA-256 hash of opsec-26.3+v1.1.7.4.jar?
The SHA-256 fingerprint of opsec-26.3+v1.1.7.4.jar is ca06658887d3fe61f4a35f6062f7e6e7ccacefcb4f3a60b20d288e5e5cf6831f, and its MD5 is 3caecdbb19621c121e51b0d1f1324c71. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
Is it safe to open or run opsec-26.3+v1.1.7.4.jar?
We found nothing harmful in opsec-26.3+v1.1.7.4.jar. The main caveat is where you got it: attackers sometimes spread malware under the name of real software, so get it from the official website. If your own antivirus warns about it, check the source before you ignore the warning.
How up to date is this analysis of opsec-26.3+v1.1.7.4.jar?
This report reflects the scan on Nov 17, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Recent reports on other files with the same rating.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.