File scan report
Verdict Safe
Is 1trouser-
No antivirus engine detected the established JAR, while one sandbox exposed limited behavioral concerns that lack malicious host, child, or research corroboration.
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the project's own website.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 52 flagged
- Flagged 0
- No detection 52
- No result 22
- Code signing Not applicable
- Test run Completed
- First seen 9mo ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 52 antivirus engines that checked it flagged this JAR, including the reporting major antivirus engines, and it has circulated through 362 sources over 231 days.
The strongest evidence is broad antivirus silence: 0 of the 52 antivirus engines that checked it reported a malicious or suspicious result. The file is also established rather than with 411 submissions from 362 sources over 231 days. One completed sandbox run did not issue a malicious verdict, and none of six inspected files it created was identified as malicious. However, the run mapped activity to 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 the 52 antivirus engines that checked it flagged the JAR as malicious or suspicious. 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 security software enabled and use an isolated game or Java profile if the source cannot be independently confirmed.
Where this verdict could be wrong3 caveats
- The sandbox's offensive-technique list contains and T1562.001, techniques associated with service manipulation and impairment of defenses.
- One of our behaviour rules fired for 162.159.36.2, and the missing contacted-host reputation result leaves that IP without a complete saved reputation cross-check.
- All six inspected files it created have unknown individual verdicts, despite the absence of a known-malicious dropped file.
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/52 antivirus engines reported a malicious or suspicious result.
- No major antivirus engines flagged it and 11 major antivirus engines reported it clean.
- Established prevalence: 362 sources and 411 submissions over 231 days.
- No sandbox returned a malicious verdict.
- No malicious file it created or external-intelligence hit was identified.
- Sandbox activity included offensive-class techniques and T1562.001.
- No contacted-host reputation result was saved, so complete reputation coverage for the observed IP is unavailable.
- Six files it created retain unknown individual verdicts.
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 10sandbox rule tags
- 4spawned processes
- 0network contacts
- 13filesystem & mutex artifacts
Includes 10 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 52 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 8, 2026, 4:02 PM UTC
- SHA-256
4bf12f7e7cdcc22703c3c4a20054c71215b50d3822e454263b8cdea6a9414827- SHA-1
83d6b70783243a6dd40bc38ea175f27c2790a5e1- MD5
7b665fcadf58ca531595b8c052e1b8cc
About this file
1trouser-streak-1.5.8-1.21.11.jar is a JAR file of 738.4 kB.
- Type and size
- JAR · 738.4 kB
- Signer
- Not applicable
- First seen
- Jan 20, 2026On VirusTotal.
- Submitted by
- 362 distinct sources
First scanned
Includes every engine result (74) and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
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.