Is 1trouser-streak-1.5.8-1.21.11.jar safe?
No antivirus engine detected the established JAR, while one sandbox exposed limited behavioral concerns that lack malicious host, child, or research corroboration.
None of 74 antivirus engines flagged this JAR, including the reporting tier-1 products, and it has circulated through 362 sources over 231 days. One sandbox recorded two offensive-class techniques and direct-IP traffic, but it issued no malicious verdict and no inspected child was identified as malware.
4bf12f7e7cdcc22703…8cdea6a9414827Recommended 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 this JAR, including the reporting tier-1 products, and it has circulated through 362 sources over 231 days. One sandbox recorded two offensive-class techniques and direct-IP traffic, but it issued no malicious verdict and no inspected child was identified as malware.
The strongest evidence is broad antivirus silence: 0 of 74 engines reported a malicious or suspicious result. The file is also established rather than newly observed, with 411 submissions from 362 sources over 231 days. One completed sandbox run did not issue a malicious verdict, and none of six inspected dropped children was identified as malicious. However, the run mapped activity to T1543.002 and T1562.001 and contacted 162.159.36.2 directly. Because no complete host-reputation cross-check was saved and the children retain unknown individual verdicts, those limitations warrant routine source verification despite the otherwise reassuring evidence.
What We Detected
None of 74 antivirus engines flagged the JAR as malicious or suspicious. Eleven tier-1 engines reported no detection, and no engine family consensus, hacktool label, curated intelligence hit, or YARA rule match was present. The sample has also been submitted 411 times by 362 sources over 231 days, indicating established circulation.
Threat Behavior
One completed sandbox run produced no malicious sandbox verdict. It nevertheless mapped activity to T1543.002 and T1562.001 and observed direct contact with 162.159.36.2. No complete saved host-reputation result is available for that IP. Six dropped files were inspected without a malicious-child finding, although their individual verdicts remain unknown.
What To Do Now
Obtain the JAR from its official project or distribution page and verify its SHA-256 value before running it. Keep endpoint protection enabled and use an isolated game or Java profile if the source cannot be independently confirmed.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques contains T1543.002 and T1562.001, techniques associated with service manipulation and impairment of defenses.
- MalwareTips.Synth.DirectIpC2 fired for 162.159.36.2, and contactedHosts=null leaves that IP without a complete saved reputation cross-check.
- All six inspected 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 antivirus engines reported a malicious or suspicious result.
- engines.tier1Malicious=0 and engines.tier1ReportedClean=11.
- Established prevalence: 362 sources and 411 submissions over 231 days.
- behaviour.hasMaliciousSandboxVerdict=false.
- No malicious dropped child or external-intelligence hit was identified.
- Sandbox activity included offensive-class techniques T1543.002 and T1562.001.
- Direct-IP contact to 162.159.36.2 triggered MalwareTips.Synth.DirectIpC2.
- contactedHosts=null, so complete reputation coverage for the observed IP is unavailable.
- Six dropped children retain unknown individual verdicts.
Use the file only if it came from the official project or another trusted distribution channel, and verify SHA-256 4bf12f7e7cdcc22703c3c4a20054c71215b50d3822e454263b8cdea6a9414827. Keep endpoint protection enabled.
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
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
- 10MITRE ATT&CK techniques
- 11spawned processes
- 1network contacts
- 13filesystem & 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
1trouser-streak-1.5.8-1.21.11.jar
4bf12f7e7cdcc22703c3c4a20054c71215b50d3822e454263b8cdea6a9414827
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\runtime.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
6912
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6912
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>\6912
- 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\4376
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\6720
- /tmp/hsperfdata_root/4982
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- fd40020ac41835ee0ddb…43b63fNever scannednever seen before
- 466f233cbe91ceab2bcc…5bde80Never scannednever seen before
- 3f8096f14540c8e18e4e…ad10b8Never 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
- 362sources 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 a long, established submission history across 362 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 411 times from 362 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: 1trouser-streak-1.5.8-1.21.11.jar — 4bf12f7e7cdcc22703c3c4a20054c71215b50d3822e454263b8cdea6a9414827
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\runtime.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: 6912 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6912
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
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- 1trouser-streak-1.5.8-1.21.11.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 721.0 KB
- Last analyzed
- Sep 8, 2026, 4:02 PM UTC
4bf12f7e7cdcc22703c3c4a20054c71215b50d3822e454263b8cdea6a9414827Safety & 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 1trouser-streak-1.5.8-1.21.11.jar safe?
What is 1trouser-streak-1.5.8-1.21.11.jar?
How many antivirus engines detected 1trouser-streak-1.5.8-1.21.11.jar?
What is the SHA-256 hash of 1trouser-streak-1.5.8-1.21.11.jar?
Is it safe to open or run 1trouser-streak-1.5.8-1.21.11.jar?
How up to date is this analysis of 1trouser-streak-1.5.8-1.21.11.jar?
Community
Member reviews and reports for this exact file hash.