File scan report
Verdict Safe
Is Wurst-
No antivirus engine flagged this widely submitted JAR, and its single sandbox run produced no malicious verdict or confirmed injection target.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
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.
Antivirus results
0 of 66 flagged
- Flagged 0
- No detection 66
- No result 9
- Code signing Not applicable
- Test run Completed
- First seen 21d ago
Chapter 02
Why we think so
2 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 66 antivirus engines that checked it flagged the file, including all 17 major antivirus engines represented in the results. Although the sandbox mapped possible process injection and service activity, it found no injected target, persistence indicator, malicious child, or sample-generated network contact.
The strongest evidence is broad antivirus silence: none of the 66 antivirus engines that checked it flagged the JAR, and there is no family consensus. The hash is but already appears across 148 submitting sources, which is more consistent with broadly distributed software than an isolated payload. One completed sandbox run returned a clean result and did not identify any injected process or persistence indicator. Its only recorded domain was explicitly attributed to analysis-environment background traffic, not to the sample. The and mappings remain cautionary signals, but they are insufficiently specific and are not corroborated by engines, external intelligence, or a malicious child verdict.
What We Detected
None of the 66 antivirus engines that checked it flagged the JAR, including the major antivirus engines represented in the results. No named malware family, malware-specific YARA rule, or external malware-feed match was reported. The hash has also been submitted by 148 distinct sources, indicating broad distribution despite its recent first appearance.
Threat Behavior
One sandbox run completed without a malicious verdict. It mapped T1055 and T1543.002, but no injected target process, persistence indicator, or malicious file it created was established. The only recorded domain was identified as background traffic from the analysis environment, so it is not attributed to the sample. Nine extracted files have no saved classifications and therefore remain unverified.
What To Do Now
Use the file only if it came from the expected project or distribution channel, and keep security software enabled. Because this is a Java client modification, review its requested permissions and retain the exact hash before running it on an important account or system.
Where this verdict could be wrong2 caveats
- The sandbox mapped and T1543.002, two offensive-use techniques, although it identified neither an injected process nor a persistence indicator.
- Nine extracted files lack saved verdicts, so their safety remains unverified rather than established.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 66 antivirus engines that checked it flagged the file.
- All 17 major antivirus engines represented in the results were silent.
- The single completed sandbox run did not return a malicious result.
- No malicious file it created or persistence indicator was identified.
- The hash was submitted by 148 distinct sources, indicating broad prevalence.
- The sandbox mapped possible process injection and service-related activity, but did not establish a target, method, or persistence mechanism.
- The file was first observed only seven days before this analysis.
6 sources checked · all complete. 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- 16sandbox rule tags
- 3spawned processes
- 0network contacts
- 17filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
16MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1055· Process injection
- T1059· Runs commands
- T1064
- T1074
- T1082· System recon
- T1105· Network file transfer
- T1106
- T1129· Loads modules
- T1202
- T1518.001· Checks your AV
- T1543.002· Service install
- T1564· Hides artifacts
- T1564.001· Hides artifacts
- T1564.003· Hides artifacts
- T1574· Execution hijack
Observed activity
Processes started
3Programs the file ran, with their command lines.
javaw.exe"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"cmd.exeC:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -jar "C:\Users\user\Desktop\sample.jar""java.exe"C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -jar "C:\Users\user\Desktop\sample.jar"
Files
17Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\4660 - Written
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp - Written
C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp - Written
C:\Users\user\AppData\Local\Temp\hsperfdata_user - Written
C:\Users\user\AppData\Local\Temp\hsperfdata_user\4348 - Written
\Device\ConDrv
Show all 17 entries for files
- Written
\Device\ConDrv\\Connect - Written
C:\Users\user\AppData\Local\Temp\hsperfdata_user\7012 - Written
/proc/3562/coredump_filter - Written
/tmp/hsperfdata_root/3562 - Written
/var/log/auth.log.1.gz - Written
/var/log/dpkg.log.1.gz - Written
/var/log/kern.log.1.gz - Written
/var/log/syslog.1.gz - Deleted
C:\Users\user\AppData\Local\Temp\hsperfdata_user\208 - Deleted
C:\Users\user\AppData\Local\Temp\hsperfdata_user\4996 - Deleted
/tmp/hsperfdata_root/3562
Sandbox background — not the file
13The analysis machine's own processes and connections, recorded in every run.
- VM process
icacls.exeC:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M - VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 - VM process
gzip/bin/gzip - VM process
sh/bin/sh sh -c "\n\t\tinvoke-rc.d --quiet cups restart > /dev/null\n" logrotate_script "/var/log/cups/*log " - VM process
invoke-rc.d/usr/sbin/invoke-rc.d invoke-rc.d --quiet cups restart - VM process
runlevel/sbin/runlevel
Show all 13 entries for sandbox background — not the file
- VM process
systemctl/usr/bin/systemctl systemctl --quiet is-enabled cups.service - VM process
ls/usr/bin/ls ls /etc/rc[S2345].d/S[0-9][0-9]cups - VM process
systemctl/usr/bin/systemctl systemctl --quiet is-active cups.service - VM process
sh/bin/sh sh -c /usr/lib/rsyslog/rsyslog-rotate logrotate_script /var/log/syslog - VM process
rsyslog-rotate/usr/lib/rsyslog/rsyslog-rotate - VM process
systemctl/usr/bin/systemctl systemctl kill -s HUP rsyslog.service - VM host
nexusrules.officeapps.live.com
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache. 4 have no saved verdict and were not checked; that is missing coverage, not a finding.
- e4d3e415cc56b11fde5e…5398b4Not checkedno saved verdict
- 689be1d28f03b7b49a79…a0e566Not checkedno saved verdict
- 72973b05d53f474f295d…2cb153Not checkedno saved verdict
- ce5c329f523c90f54d58…793b06Not checkedno saved verdict
Chapter 04
Technical details
None of the 66 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 12, 2026, 11:30 PM UTC
- SHA-256
41c4414c2b7e10344e34ee94f78838b7e167abcbbef046dce4457889c8d85fa3- SHA-1
a0a065674e0bd4d8afd5faaad7133d39b0abc223- MD5
d7055412407480bb45a758c2d9a8707f
About this file
Wurst-Client-v7.56-MC26.3.jar is a JAR file of 1.9 MB.
- Type and size
- JAR · 1.9 MB
- Signer
- Not applicable
- First seen
- Oct 5, 2026On VirusTotal.
- Submitted by
- 148 distinct sources
First scanned
Antivirus consensus
0 of 66 engines flagged this file
9 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-235 engines0flagged
- Low-trust13 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileClean
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookClean
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
How widely this file has been seen
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Wurst-Client-v7.56-MC26.3.jar safe?
What is Wurst-Client-v7.56-MC26.3.jar?
How many antivirus engines detected Wurst-Client-v7.56-MC26.3.jar?
What is the SHA-256 hash of Wurst-Client-v7.56-MC26.3.jar?
Is it safe to open or run Wurst-Client-v7.56-MC26.3.jar?
How up to date is this analysis of Wurst-Client-v7.56-MC26.3.jar?
Community
Member reviews and reports for this exact file hash.