Is symbol-chat-1.21.11-1.3.13.jar safe?
No engine detected this moderately distributed JAR, and its completed sandbox run found no malicious outcome, though one direct IP contact remains unverified.
None of 74 antivirus engines flagged the JAR, including 17 tier-1 engines, and the completed sandbox run issued no malicious verdict. Two offensive techniques and direct traffic to one IP warrant some caution because a complete host-reputation check was not available.
7c0216484d6414beef…eb163f18be4d7eRecommended 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 74 antivirus engines flagged the JAR, including 17 tier-1 engines, and the completed sandbox run issued no malicious verdict. Two offensive techniques and direct traffic to one IP warrant some caution because a complete host-reputation check was not available.
The strongest evidence is the complete absence of detections across 74 antivirus engines, including 17 tier-1 products. One completed sandbox run produced no malicious verdict, and no malicious dropped child was identified among six inspected files. The sample has also circulated through 28 sources and 31 submissions, reducing concern that it is an entirely new artifact. Counter-signals include T1543.002, T1562.001, and a low-severity direct-IP heuristic for 162.159.36.2. Because contactedHosts is unavailable and all six child verdicts remain individually unknown, the network and child-file evidence is not fully conclusive.
What We Detected
No antivirus engine flagged the file: 0 of 74 reported a malicious or suspicious result, including all 17 tier-1 engines. The JAR has appeared from 28 sources across 31 submissions, indicating moderate circulation.
Threat Behavior
One completed sandbox run did not produce a malicious verdict. It nevertheless recorded T1543.002 and T1562.001, plus low-severity direct traffic to 162.159.36.2. No complete host-reputation result is available because the contacted-host cross-check was not saved. Six dropped files were inspected without an identified malicious child, but their individual verdicts remain unknown.
What To Do Now
Obtain the JAR from its official project or distribution channel and verify its SHA-256 before running it. Keep endpoint protection enabled, and use an isolated environment if the source cannot be confirmed.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques includes T1543.002 and T1562.001, which can indicate service manipulation and impaired defenses, although the sandbox produced no malicious verdict.
- The sample contacted 162.159.36.2 directly, and contactedHosts=null means no complete reputation assessment is available for that address.
- All six dropped children have unknown individual verdicts despite droppedChildren.hasMaliciousChild=false.
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 engines reported a malicious or suspicious result.
- All 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false in one completed run.
- droppedChildren.hasMaliciousChild=false after six inspections.
- Observed across 28 sources and 31 submissions.
- Runtime evidence includes offensive techniques T1543.002 and T1562.001.
- Low-severity MalwareTips.Synth.DirectIpC2 triggered for 162.159.36.2.
- contactedHosts=null leaves the observed IP without a complete reputation check.
- Six dropped children have unknown individual verdicts.
Use the file only if its download source and SHA-256 can be verified. Keep endpoint protection enabled and isolate execution when provenance is uncertain.
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
Complete1 signature or behavior rule matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 11MITRE ATT&CK techniques
- 11spawned processes
- 1network contacts
- 13filesystem & 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.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\7068
- 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\3164
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\6504
- /tmp/hsperfdata_root/4989
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- 9de807ef65e5f8641cc2…47ce22Never scannednever seen before
- 088ad20ce12160f0e1b6…397680Never scannednever seen before
- b468bf508c1b034631c5…457d6eNever scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 44a3bab2c338e3bca24c…d3b9e7Never scannednever seen before
- ac941ead01d5451a7a9f…253227Never 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 / 74engines flagged
- 28sources 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
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 03
The hash has been submitted 31 times from 28 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: symbol-chat-1.21.11-1.3.13.jar — 7c0216484d6414beef4bd228f52ee84633403fd9968b645845eb163f18be4d7e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.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: 7068 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\7068
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.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- symbol-chat-1.21.11-1.3.13.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 436.7 KB
- Last analyzed
- Oct 7, 2026, 7:36 AM UTC
7c0216484d6414beef4bd228f52ee84633403fd9968b645845eb163f18be4d7eSafety & 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 symbol-chat-1.21.11-1.3.13.jar safe?
What is symbol-chat-1.21.11-1.3.13.jar?
How many antivirus engines detected symbol-chat-1.21.11-1.3.13.jar?
What is the SHA-256 hash of symbol-chat-1.21.11-1.3.13.jar?
Is it safe to open or run symbol-chat-1.21.11-1.3.13.jar?
How up to date is this analysis of symbol-chat-1.21.11-1.3.13.jar?
Community
Member reviews and reports for this exact file hash.