Is Pixie Client (1).jar safe?
No engine detected the JAR, and one completed sandbox run produced no malware finding despite an isolated service-related technique.
All 74 antivirus engines returned no detection, including 17 high-trust engines. One sandbox run found no malicious outcome, and neither external intelligence nor inspected child files supplied corroborating evidence, though the file remains relatively recent and one service-related technique was recorded.
1b18a126a2fe1e8053…b24070962295e9Recommended 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 returned no detection, including 17 high-trust engines. One sandbox run found no malicious outcome, and neither external intelligence nor inspected child files supplied corroborating evidence, though the file remains relatively recent and one service-related technique was recorded.
The strongest evidence is unanimous antivirus silence: 0 of 74 engines flagged the sample, including all 17 high-trust engines. A completed sandbox run did not produce a malware finding and recorded no network contacts. The service-related T1543.002 observation is worth noting, but no persistence indicators were recorded and the surrounding activity appears consistent with routine system operations. Five child files were inspected without a malicious child finding, although their individual classifications remain unknown. No matching malware family, researcher rule, or known-malicious intelligence entry corroborates harmful intent.
What We Detected
None of 74 antivirus engines flagged the JAR, and all 17 high-trust engines reported no detection. External checks also returned no MalwareBazaar match, CIRCL hit, or YARAify rule match.
Threat Behavior
One completed sandbox run did not issue a malicious verdict and recorded no contacted domains, IP addresses, or URLs. It observed T1543.002, a service-related technique that can be abused for persistence, but recorded no persistence indicators; the listed processes mainly involve routine log rotation and CUPS service checks. Five dropped files were inspected without a malicious child finding, although their individual verdicts remain unknown. No complete contacted-host reputation result is available.
What To Do Now
Keep endpoint protection enabled and obtain the JAR from a trusted source. If its origin or purpose is unclear, test it in an isolated environment and monitor future scans because the sample has only a short submission history.
Where this verdict could be wrong4 caveats
- behaviour.offensiveTechniques includes T1543.002, a service-related technique that can support persistence, although persistenceIndicators is empty.
- All 5 inspected dropped children have unknown individual verdicts, so their harmlessness was not affirmatively established.
- contactedHosts is null, so no completed host-reputation cross-check is available; however, the sandbox recorded no contacted domains, IPs, or URLs.
- The file was first submitted 14 days ago and has only 4 submissions, limiting its established history.
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 returned no detection.
- One completed sandbox run produced no malicious verdict.
- No domains, IP addresses, or URLs were observed during the sandbox run.
- No external-intelligence or malicious-child corroboration was found.
- behaviour.offensiveTechniques includes T1543.002.
- The sample was first submitted 14 days ago.
- All 5 dropped children have unknown individual verdicts.
- contactedHosts is null, so host-reputation coverage was not completed.
The evidence supports ordinary use if the JAR came from an expected source. Keep protection enabled and avoid granting elevated privileges unless the software's origin and function are verified.
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
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/3578/coredump_filter
- /tmp/hsperfdata_root/3578
- /var/log/auth.log.1.gz
- /var/log/dpkg.log.1.gz
- /var/log/kern.log.1.gz
- /tmp/hsperfdata_root/3578
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
- 4sources 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 4 times from 4 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Pixie Client (1).jar — 1b18a126a2fe1e80539f4660246e906615322f111a0d0c7b9cb24070962295e9
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/3578/coredump_filter
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 3578 — /tmp/hsperfdata_root/3578
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Pixie Client (1).jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 1.9 MB
- Last analyzed
- Oct 3, 2026, 11:36 PM UTC
1b18a126a2fe1e80539f4660246e906615322f111a0d0c7b9cb24070962295e9Safety & 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 Pixie Client (1).jar safe?
What is Pixie Client (1).jar?
How many antivirus engines detected Pixie Client (1).jar?
What is the SHA-256 hash of Pixie Client (1).jar?
Is it safe to open or run Pixie Client (1).jar?
How up to date is this analysis of Pixie Client (1).jar?
Community
Member reviews and reports for this exact file hash.