File scan report
Verdict Safe
Is sydney-
No antivirus engine flagged this JAR, and its completed sandbox run returned clean, though several unconfirmed offensive-technique mappings warrant routine source verification.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Use the file only if it came from the expected project or a trusted distribution channel. Keep security protection enabled and isolate execution when provenance cannot be verified.
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 65 flagged
- Flagged 0
- No detection 65
- No result 10
- Code signing Not applicable
- Test run Completed
- First seen 1mo 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 65 antivirus engines that checked it flagged the file, including all 17 reporting major antivirus engines, and the completed sandbox run returned clean. The sandbox mapped three potentially offensive techniques, but it identified no injected process, persistence indicator, malicious child, or malware-specific research rule.
None of the 65 antivirus engines that checked it flagged the JAR, so there is no engine-supported malware family or category. One completed sandbox run returned clean and recorded no persistence indicators or injected target processes. Research feeds supplied no malware-specific YARA rules or repository match. Eight dropped files have no saved verdicts, and no complete contacted-host reputation result is available, so those areas should not be treated as fully cleared.
What We Detected
None of the 65 antivirus engines that checked it flagged the JAR, including all 17 reporting major antivirus engines. No engine supplied a malware-family label, and research intelligence returned no malware-specific YARA rule or repository match.
Threat Behavior
One completed sandbox run returned clean. It mapped T1055, T1543.002, and T1562.001, but no injected target process, persistence indicator, or malicious sandbox conclusion was recorded. The sole recorded IP contact was explicitly identified as analysis-environment background traffic, while a complete host-reputation cross-check is unavailable. Eight dropped files also lack saved verdicts, so they represent missing coverage rather than evidence of harm.
What To Do Now
Obtain the JAR from the expected project or distribution channel and verify its published hash when possible. Keep security software enabled and use an isolated environment if the source is uncertain or the requested permissions appear unrelated to the software's purpose.
Where this verdict could be wrong3 caveats
- The sandbox mapped process injection, service execution, and defense impairment techniques, which deserve caution even though no injection target, persistence indicator, or malicious sandbox verdict was recorded.
- Eight dropped files lack saved verdicts, so their safety has not been established.
- Host-reputation checking was not completed or retained, although the only recorded contact was identified as analysis-environment background traffic.
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 65 antivirus engines that checked it flagged the file.
- All 17 reporting major antivirus engines were silent.
- The completed sandbox run returned clean and recorded no persistence indicators.
- No malware-specific research rule or malware-repository match was found.
- No file it created has a saved malicious classification.
- The sandbox mapped possible process injection, service execution, and defense impairment activity, although it did not identify an injection target or confirm hostile intent.
- Eight files created or extracted during analysis have no saved classifications.
- A complete reputation check for observed hosts is unavailable.
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- 16sandbox rule tags
- 3spawned processes
- 0network contacts
- 15filesystem & 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.
- T1006
- 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
- T1562.001· Disables security
- T1564· Hides artifacts
- T1564.001· Hides artifacts
- T1564.003· Hides artifacts
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\runtime.jar"cmd.exeC:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\download.jar"" >> C:\cmdlinestart.log 2>&1java.exe"C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\download.jar"
Files
15Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5088 - 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\7060 - Written
C:\cmdlinestart.log
Show all 15 entries for files
- Written
\Device\ConDrv\\Connect - Written
/proc/3532/coredump_filter - Written
/tmp/hsperfdata_root/3532 - 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\5080 - Deleted
/tmp/hsperfdata_root/3532
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
162.159.36.2
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache. 3 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 1097ee99275d75c19f47…1a0fe0Not checkedno saved verdict
- 37e1823352f6547fc5c6…293c4eNot checkedno saved verdict
- 1d7fe1a320cdb2fdde26…28e4f0Not checkedno saved verdict
Chapter 04
Technical details
None of the 65 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
- Oct 16, 2026, 4:02 AM UTC
- SHA-256
f023a37d7bdc5f55412b0b407607a5132012cfb1379605f981b7b342b55ac51e- SHA-1
6f1cda6f8884798aae28f3d46c455183b55ee3b5- MD5
adcb74704e866f233ee2a4c749424fda
About this file
sydney-loader+mc26.1-26.1.2.jar is a JAR file of 10.2 MB.
- Type and size
- JAR · 10.2 MB
- Signer
- Not applicable
- First seen
- Aug 28, 2026On VirusTotal.
- Submitted by
- 18 distinct sources
First scanned
Antivirus consensus
0 of 65 engines flagged this file
10 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-234 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
- TrustlookNo result
- 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is sydney-loader+mc26.1-26.1.2.jar safe?
What is sydney-loader+mc26.1-26.1.2.jar?
How many antivirus engines detected sydney-loader+mc26.1-26.1.2.jar?
What is the SHA-256 hash of sydney-loader+mc26.1-26.1.2.jar?
Is it safe to open or run sydney-loader+mc26.1-26.1.2.jar?
How up to date is this analysis of sydney-loader+mc26.1-26.1.2.jar?
Community
Member reviews and reports for this exact file hash.