Is Origo-Client-26.2.jar safe?
No antivirus engine detected this new JAR, but sensitive runtime mappings and an unchecked direct-IP contact warrant caution until its origin is verified.
None of 74 antivirus engines detected the file, and the completed sandbox did not issue a malicious conclusion. However, the sample is newly observed, mapped to three offensive techniques, and contacted an IP whose reputation was not checked, so its source and purpose should be verified before execution.
ad02c36ca23d35e0c1…e09694523f44e5Recommended next actions
Before opening or running
Do not open or run it until the source and publisher can be verified independently.
If you already opened or ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the publisher's official site and verify its exact hash when possible.
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 74 antivirus engines detected the file, and the completed sandbox did not issue a malicious conclusion. However, the sample is newly observed, mapped to three offensive techniques, and contacted an IP whose reputation was not checked, so its source and purpose should be verified before execution.
The strongest favorable evidence is that 0 of 74 engines detected the sample, including all 17 tier-1 engines. One completed sandbox produced no malicious conclusion, and none of nine inspected child hashes was identified as malware. However, runtime evidence maps activity to T1055, T1543.002, and T1562.001, which can involve process injection, service modification, and interference with security controls. 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. Its recent appearance, low prevalence, and lack of similar-file history leave these conflicting signals unresolved.
What We Detected
No detections were reported by 74 antivirus engines, including 17 tier-1 engines. External intelligence also contained no CIRCL, MalwareBazaar, or YARAify match. The file is only six days old in the available records and has been submitted twice by two sources, so it has little established history.
Threat Behavior
One completed sandbox did not produce a malicious conclusion. Nevertheless, its runtime mappings include T1055, T1543.002, and T1562.001, covering potentially sensitive behavior such as process injection, service modification, and impairment of defenses. It also contacted 162.159.36.2 directly; because contactedHosts is null, no complete reputation result is available for that connection. Nine child files were inspected without a malware finding, but all nine remain without definitive child verdicts.
What To Do Now
Verify the JAR against the developer's official release channel and confirm its SHA-256 before running it. Keep endpoint protection enabled and, if its origin cannot be established, test it only in an isolated environment without credentials or sensitive data.
Where this verdict could be wrong3 caveats
- The absence of detections across 74 engines weighs strongly against known malware, including no alerts from the 17 tier-1 engines.
- The only completed sandbox did not issue a malicious verdict, but one run provides limited behavioral coverage.
- External intelligence returned no CIRCL, MalwareBazaar, or YARAify hit, although absence of a hit does not establish benign intent.
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 of 74 antivirus engines detected the file
- All 17 tier-1 engines reported no detection
- The completed sandbox did not issue a malicious conclusion
- No inspected child was identified as malicious
- No CIRCL, MalwareBazaar, or YARAify match was found
- Only six days of observed history and two submissions
- Runtime mapping to T1055 process injection
- Runtime mapping to T1543.002 service modification
- Runtime mapping to T1562.001 impairment of defenses
- Direct contact with 162.159.36.2 without a completed reputation check
- No signing or publisher assurance is available for this JAR
Obtain the JAR only from the developer's official channel and compare SHA-256 ad02c36ca23d35e0c1860f876b255b6d03dbb806a26d649553e09694523f44e5. Keep security protection enabled and avoid normal-system execution if the source cannot be authenticated.
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
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
- 14filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Created or modified a system service, which can keep code running.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Transferred a file over the network; malware can use this to fetch additional payloads.
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
Origo-Client-26.2.jar
ad02c36ca23d35e0c1860f876b255b6d03dbb806a26d649553e09694523f44e5
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.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
2660
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2660
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>\2660
- 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\6392
- /tmp/hsperfdata_root/3557
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- fb411525bdcee35f8b9c…82ee99Never scannednever seen before
- 18cc63bb913ac11360c9…217618Never scannednever seen before
- 9e6d7d13acc3f06bc1e3…611c17Never 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.
- 2rule hits recorded
- 0 / 74engines flagged
- 2sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 2 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Origo-Client-26.2.jar — ad02c36ca23d35e0c1860f876b255b6d03dbb806a26d649553e09694523f44e5
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.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: 2660 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2660
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\download.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 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
- Origo-Client-26.2.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 1.5 MB
- Last analyzed
- Sep 27, 2026, 2:26 AM UTC
ad02c36ca23d35e0c1860f876b255b6d03dbb806a26d649553e09694523f44e5Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open or run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this Java file and use a fresh copy from a trusted source. Get a fresh copy from the publisher's official site and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Origo-Client-26.2.jar safe, or is it malware?
What is Origo-Client-26.2.jar?
How many antivirus engines detected Origo-Client-26.2.jar?
I already downloaded and opened or ran Origo-Client-26.2.jar — what should I do?
How do I remove Origo-Client-26.2.jar?
What is the SHA-256 hash of Origo-Client-26.2.jar?
How up to date is this analysis of Origo-Client-26.2.jar?
Community
Member reviews and reports for this exact file hash.