File scan report
Verdict Suspicious
Is Anubis_ Beta_ 0. 9. 9. 1. jar safe? Treat it as suspicious.
None of the 65 antivirus engines that checked it flagged this day-old Java archive, but one sandbox run labelled it a trojan while another returned clean, leaving the evidence…
Read the whole reasonShow less
Why Suspicious? One sandbox test run rated it malicious while another found nothing; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Only run this Java archive if it came directly from a source you trust; otherwise hold off and rescan later as more evidence accumulates.
What to do now5 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open or run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
It is only 5 days old. If you're unsure, scan it again in a few days; antivirus engines often catch up on new files.
If you already opened or ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 65 flagged
- Flagged 0
- No detection 65
- No result 10
- Code signing Not applicable
- Test run Completed
- First seen 5d ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
No antivirus engine in our network detected this Java archive, and no threat databases list it. However, one sandbox run reported it as a trojan while another found nothing wrong, and nothing else backs either result. The file was first seen on Oct 20, 2026, so there is not enough evidence to clear or condemn it.
Across three sandbox runs, one returned a malicious verdict and another returned clean, so the evidence from the test run disagrees. No injection target, high-risk technique, malicious contacted host or malicious dropped file supports the malicious run. No public malware databases or community rules list the file. Because the file is very new and has no publisher signature or prior history, the evidence is too thin for a confident call either way.
What We Detected
This Java archive was first seen on Oct 20, 2026 and has been submitted by 12 sources. None of the 65 antivirus engines that checked it flagged it, and it does not appear in public malware databases or community rule sets.
Threat Behavior
Three sandbox runs launched the archive with Java. One labelled it a trojan; another returned clean. The runs recorded Java starting a second runtime archive through a command prompt and ordinary Java temp files, but no named process injection, persistence or high-risk techniques. The hosts it contacted have no malicious reputation in our records.
What To Do Now
If you did not obtain this from the official developer, do not run it. If you need it, verify the source, wait for further analysis, or run it only in an isolated environment with your security software kept enabled.
Where this verdict could be wrong2 caveats
- One sandbox run labelled the file as a trojan, and fresh Java archives are often missed by antivirus engines, so a new threat cannot be excluded.
- Conversely, none of the 65 antivirus engines that checked it flagged it and another sandbox run returned clean, which may mean the malicious run reacted to generic Java launcher activity.
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.
- Another sandbox run returned a clean result.
- No listing in public malware databases or matches in malware-specific rules.
- Contacted hosts have no malicious or suspicious reputation in our records.
- One of three sandbox runs labelled the file as a trojan.
- The file is very new, first seen on Oct 20, 2026, with no publisher history.
- When it ran it launches a second Java archive through a command prompt.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 3 isolated tests; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 16sandbox rule tags
- 4spawned processes
- 2network contacts
- 11filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Downloaded a file during the test run.
Moderate concern: Hid files or windows on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Loaded extra code modules while running.
Note: Checked which security software was installed on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
Anubis_Beta_0.9.9.1.jar
6f3b38fa2ac482d86190abdf4290a3e57122507f76faf5c28bbacb34d02664a6
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
javaw.exe
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
Test run - Evidence 3 of 7: ProcessSeen in the test run
cmd.exe
C:\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\runtime.jar""
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
1084
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\1084
Test run - Evidence 5 of 7: Written fileSeen in the test run
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
shed.s-0005.dual-s-dc-msedge.net
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
s-0005.dual-s-dc-msedge.net
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 3 sandboxes and the results were split: 1 returned "malicious" and 1 returned "clean".
Sandbox verdicts
2- VT: MALWARE, TROJANmalicious
- 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
4Programs 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\runtime.jar""java.exe"C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -jar "C:\Users\user\Desktop\runtime.jar"java/usr/bin/java -jar /tmp/sample.jar
Network contacts
22 hosts, listed as 2 domains. Links show the host and path only.
- Domain
shed.s-0005.dual-s-dc-msedge.net - Domain
s-0005.dual-s-dc-msedge.net
Files
11Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\1084 - 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\6936 - Written
\Device\ConDrv
Show all 11 entries for files
- Written
\Device\ConDrv\\Connect - Written
/proc/3571/coredump_filter - Written
/tmp/hsperfdata_root/3571 - Deleted
C:\Users\user\AppData\Local\Temp\hsperfdata_user\1672 - Deleted
/tmp/hsperfdata_root/3571
Sandbox background — not the file
8The 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 /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
Show all 8 entries for sandbox background — not the file
- VM process
sh/bin/sh sh -c /usr/lib/rsyslog/rsyslog-rotate logrotate_script /var/log/mail.info/var/log/mail.warn/var/log/mail.err/var/log/mail.log/var/log/daemon.log/var/log/kern.log/var/log/auth.log/var/log/user.log/var/log/lpr.log/var/log/cron.log/var/log/debug/var/log/messages - VM host
eip-terr-na.cdp1.digicert.com.akahost.net
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.
- 7d736b5365c480951ae2…c9e526Not checkedno saved verdict
- ec5eb769e72e35433cd2…9f62c7Not checkedno saved verdict
- 833a3fab35c8db035ceb…2daf36Not 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 · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 21, 2026, 8:14 AM UTC
- SHA-256
6f3b38fa2ac482d86190abdf4290a3e57122507f76faf5c28bbacb34d02664a6- SHA-1
349f5dce1a7dc31349b6fb21d663bd391a5f95cb- MD5
8ec0a313003f80db06fa97a5b7720adb
About this file
Anubis_Beta_0.9.9.1.jar is a JAR file of 23.4 MB.
- Type and size
- JAR · 23.4 MB
- Signer
- Not applicable
- First seen
- Oct 20, 2026On VirusTotal.
- Submitted by
- 12 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-235 engines0flagged
- Low-trust12 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
- BkavNo result
- CAT-QuickHealClean
- ClamAVNo result
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebClean
- ElasticClean
- 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
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 Anubis_Beta_0.9.9.1.jar safe, or is it malware?
What is Anubis_Beta_0.9.9.1.jar?
How many antivirus engines detected Anubis_Beta_0.9.9.1.jar?
I already downloaded and opened or ran Anubis_Beta_0.9.9.1.jar — what should I do?
What is the SHA-256 hash of Anubis_Beta_0.9.9.1.jar?
How up to date is this analysis of Anubis_Beta_0.9.9.1.jar?
Community
Member reviews and reports for this exact file hash.