Is OdinClient-26.2.jar safe?
No antivirus engine detected this JAR, and one sandbox produced no malicious verdict, though its newness and service-related activity warrant normal caution.
All 74 antivirus engines avoided a malicious or suspicious label, including 16 reporting tier-1 engines. One sandbox recorded a service-related technique but issued no malicious verdict, while the file's very recent appearance and incomplete child reputation history limit certainty.
4b253880629b092f2c…ea43538cade724Recommended 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.
All 74 antivirus engines avoided a malicious or suspicious label, including 16 reporting tier-1 engines. One sandbox recorded a service-related technique but issued no malicious verdict, while the file's very recent appearance and incomplete child reputation history limit certainty.
Static scanning produced no detections across 74 antivirus engines, with 16 tier-1 engines reporting no detection. One completed sandbox run did not issue a malicious verdict and observed no network contacts, although it mapped service-related activity to T1543.002. Five written child hashes were inspected without a malicious finding, but all five still lack definitive individual verdicts. Research feeds supplied no YARA, malware-repository, or known-malicious reference hit. Because this hash is newly observed with only one submission and no applicable signing evidence, the absence of detections is reassuring but not an absolute guarantee.
What We Detected
No malicious or suspicious labels were returned by 74 antivirus engines. Sixteen tier-1 engines reported no detection, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Microsoft. Research intelligence also returned no YARA rules, malware-repository match, or known-malicious reference hit.
Threat Behavior
One completed sandbox run issued no malicious verdict and observed no contacted domains, IP addresses, or URLs. It mapped one action to T1543.002, which concerns service-related execution or persistence, but recorded no persistence indicators. Five written child hashes were inspected without a malicious child finding; however, their individual verdicts remain unknown, and no complete contacted-host reputation result is available.
What To Do Now
Obtain the JAR from its official project or developer channel and verify any published checksum before running it. Keep endpoint protection enabled, and use isolation if the source is unfamiliar because the file has almost no distribution history.
Where this verdict could be wrong4 caveats
- prevalence.classification=rare_new: the hash has only 1 submission and file.ageDays=0, so reputation has not yet developed.
- behaviour.offensiveTechniques contains T1543.002, a service-related technique, although persistenceIndicators is empty and no sandbox issued a malicious verdict.
- contactedHosts=null, so no complete host-reputation cross-check is available.
- similarHashes contains 5/5 prior safe verdicts, but every matchKind=filetype and the listed files are unrelated formats, making those comparisons weak.
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/74 antivirus engines returned a malicious or suspicious label.
- Sixteen tier-1 engines reported no detection.
- One sandbox issued no malicious verdict and recorded no network contacts.
- No malicious child was found among five inspected written hashes.
- CIRCL, MalwareBazaar, and YARAify supplied no corroborating hit.
- The hash is newly observed and has only one recorded submission.
- Sandbox mapping includes the offensive technique T1543.002.
- All five written child hashes currently have unknown individual verdicts.
- No complete contacted-host reputation cross-check is available.
Use the file only if it came from the expected official source, and verify a developer-published hash when available. Keep endpoint protection enabled and consider isolated execution until the file develops more reputation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
- 5MITRE ATT&CK techniques
- 12spawned processes
- 0network contacts
- 7filesystem & 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
OdinClient-26.2.jar
4b253880629b092f2c8d6ba9d53312d217320ecbea07e67324ea43538cade724
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
/bin/gzip
02Isolated runtime analysis - ProcessObserved
Observed process
/bin/sh sh -c "\n\t\tinvoke-rc.d --quiet cups restart > /dev/null\n" logrotate_script "/var/log/cups/*log "
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
coredump_filter
/proc/3556/coredump_filter
04Isolated runtime analysis - Written fileObserved
3556
/tmp/hsperfdata_root/3556
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- /proc/3556/coredump_filter
- /tmp/hsperfdata_root/3556
- /var/log/auth.log.1.gz
- /var/log/dpkg.log.1.gz
- /var/log/kern.log.1.gz
- /tmp/hsperfdata_root/3556
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- 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.
- 0rule hits recorded
- 0 / 74engines flagged
- 1sources 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 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: OdinClient-26.2.jar — 4b253880629b092f2c8d6ba9d53312d217320ecbea07e67324ea43538cade724
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — /bin/gzip
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — /bin/sh sh -c "\n\t\tinvoke-rc.d --quiet cups restart > /dev/null\n" logrotate_script "/var/log/cups/*log "
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: coredump_filter — /proc/3556/coredump_filter
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 3556 — /tmp/hsperfdata_root/3556
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- OdinClient-26.2.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 1.5 MB
- Last analyzed
- Sep 14, 2026, 9:38 AM UTC
4b253880629b092f2c8d6ba9d53312d217320ecbea07e67324ea43538cade724Safety & 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 OdinClient-26.2.jar safe?
What is OdinClient-26.2.jar?
How many antivirus engines detected OdinClient-26.2.jar?
What is the SHA-256 hash of OdinClient-26.2.jar?
Is it safe to open or run OdinClient-26.2.jar?
How up to date is this analysis of OdinClient-26.2.jar?
Community
Member reviews and reports for this exact file hash.