File scan report
Verdict Suspicious
Is Anubis Beta 0. 9. 9. 1 (1). jar safe? Treat it as suspicious.
None of the 64 antivirus engines that checked it flag this Java archive, but one of three sandbox runs returned a malicious verdict that nothing else confirms, so the evidence is…
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.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 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.
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 64 flagged
- Flagged 0
- No detection 64
- No result 11
- Code signing Not applicable
- Test run Completed
- First seen 14d ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Of three sandbox runs, one reported trojan behaviour and another came back clean. No injection target, malicious network contact or threat-database listing backs the malicious run. Without that corroboration, the evidence does not support a firm call either way.
The engines are unanimous: none of the 75 flagged the file, including all 18 major antivirus engines that returned a result. The file is rare in neither sense: nearly 2,900 sources submitted it within a week. One sandbox run labelled it a trojan while another found it clean. Threat databases and community malware rules returned no matches. Because one run disagrees and no other evidence settles the question, the file is left undecided rather than cleared.
What We Detected
None of the 64 antivirus engines that checked it flagged this Java archive, and major antivirus engines such as Kaspersky, ESET, Microsoft and BitDefender reported it clean. It is widely circulated, with nearly 2,900 submitters in its first week. Its community reputation is slightly negative, and researcher notes tag it with stealer and trojan labels.
Threat Behavior
Three sandbox runs launched the archive with Java. One run returned a malicious trojan verdict and another returned clean. The runs recorded no injection into other processes and no persistence. The only network contact was the analysis machine's background traffic.
What To Do Now
Run this file only if you obtained it from the developer's official channel and trust that source. If you are unsure, run it in a virtual machine or sandbox. Keep your antivirus enabled and rescan later, as engine detections may change.
Where this verdict could be wrong2 caveats
- One sandbox run returned a malicious trojan verdict, and community researchers tagged the file with stealer and trojan labels. Fresh Java-based threats can evade signature engines for a while.
- The file was submitted by nearly 2,900 sources in its first week with zero engine detections, which fits a widely shared tool rather than targeted malware.
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 64 antivirus engines that checked it flagged it
- All major antivirus engines that returned a result reported it clean
- Another sandbox run returned clean, with no injection or persistence observed
- No listing in malware-sharing databases or matches to malware-specific community rules
- One of three sandbox runs labelled the file a trojan
- Community researcher notes tag it with stealer and trojan labels
- Slightly negative community reputation
- First seen on Oct 11, 2026
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 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
- 0network 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: 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 downloading a file, but no download 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 5: FileSeen in the test run
Anubis Beta 0.9.9.1 (1).jar
20a03c38a39d013bf5f6836818c0b665478eb3381181fd372cd661c438fd752a
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
javaw.exe
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.jar"
Test run - Evidence 3 of 5: 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 5: Written fileSeen in the test run
5940
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5940
Test run - Evidence 5 of 5: Written fileSeen in the test run
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
Test run - +1 more recorded observation
5 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\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" -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
Files
11Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5940 - 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\6444 - Written
\Device\ConDrv
Show all 11 entries for files
- Written
\Device\ConDrv\\Connect - Written
/proc/3530/coredump_filter - Written
/tmp/hsperfdata_root/3530 - Deleted
C:\Users\user\AppData\Local\Temp\hsperfdata_user\980 - Deleted
/tmp/hsperfdata_root/3530
Sandbox background — not the file
7The 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/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 process
rsyslog-rotate/usr/lib/rsyslog/rsyslog-rotate - VM process
systemctl/usr/bin/systemctl systemctl kill -s HUP rsyslog.service
Show all 7 entries for sandbox background — not the file
- 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.
- 4889ae2ca39cae26254a…43c72cNot checkedno saved verdict
- 5399bb8ff3d86427b032…5c587cNot checkedno saved verdict
- e5ccd0a82fff62db64ba…af8e97Not checkedno saved verdict
Chapter 04
Technical details
None of the 64 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 18, 2026, 9:48 PM UTC
- SHA-256
20a03c38a39d013bf5f6836818c0b665478eb3381181fd372cd661c438fd752a- SHA-1
50548b8dd5e4d9a1a9cb99dda32ccb75a446650c- MD5
e8f5e1e4a7b4ee4e99e4518c318dc1fd
About this file
Anubis Beta 0.9.9.1 (1).jar is a JAR file of 21.2 MB.
- Type and size
- JAR · 21.2 MB
- Signer
- Not applicable
- First seen
- Oct 11, 2026On VirusTotal.
- Submitted by
- 2,898 distinct sources
First scanned
Antivirus consensus
0 of 64 engines flagged this file
11 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-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
- 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
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 Anubis Beta 0.9.9.1 (1).jar safe, or is it malware?
What is Anubis Beta 0.9.9.1 (1).jar?
How many antivirus engines detected Anubis Beta 0.9.9.1 (1).jar?
What should I do if I already opened or ran Anubis Beta 0.9.9.1 (1).jar?
What is the SHA-256 hash of Anubis Beta 0.9.9.1 (1).jar?
How up to date is this analysis of Anubis Beta 0.9.9.1 (1).jar?
Community
Member reviews and reports for this exact file hash.