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 Java archive, but one sandbox run labelled it malicious while another returned clean, so the evidence is too…
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.
Avoid running this Java application unless it comes from a trusted official source. Rescan it later as more evidence becomes available.
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 4 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 4d ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 65 antivirus engines that checked it flagged this Java application, including every major antivirus engine. However, one of the sandbox runs labelled it a trojan while another returned clean. The file is also and rarely seen, and nothing else confirms or rules out the malicious run.
The sandbox runs disagree: one returned a trojan label and another returned clean. No named injection target, high-risk technique, malicious contacted host, malicious dropped file or malware-specific rule backs up the malicious run. The file was first seen on Oct 22, 2026 from only three submitters, and Java archives are not code-signed, so there is no publisher identity to rely on.
What We Detected
None of the 65 antivirus engines that checked it flagged this Java archive, and the 18 major antivirus engines all reported it clean. One sandbox run labelled it a trojan, while another run returned clean. Public sample databases and community rule sets hold no listing for this file.
Threat Behavior
In the sandbox runs the file launched Java and a command shell to start another Java archive, and it wrote typical Java runtime files. Its tags mention checks for debugging environments and the CPU name. No injected process, persistence, or contact with known-malicious hosts was recorded, and the network contacts belonged to the analysis machine's background activity.
What To Do Now
Only run this file if you obtained it from the developer's official source and trust that source. If you are unsure, wait for more analysis or rescan it later, and keep your antivirus enabled.
Where this verdict could be wrong2 caveats
- One sandbox run labelled the sample a trojan. Fresh Java malware is often missed by antivirus engines at first, so the clean engine result does not fully exclude a threat.
- The sample tags note debug-environment and CPU-name checks, which can also appear in obfuscated or protected legitimate Java applications.
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 it, including all major antivirus engines
- Another sandbox run returned a clean result
- No injected processes, persistence, or known-malicious network contacts were observed
- One sandbox run labelled the sample a trojan
- The file is rare and was first seen on Oct 22, 2026, with only three submitters
- It checks for debugging environments and the processor name
- It launches a second Java archive through a command shell
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
- 0network contacts
- 14filesystem & 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.jar
c7bb475ffa76936407005cde0365d256eadaa6eafc9612529f61f1dabe7f9796
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\download.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
5560
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5560
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\download.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
14Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5560 - 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\7036 - Written
\Device\ConDrv
Show all 14 entries for files
- Written
\Device\ConDrv\\Connect - Written
/proc/3533/coredump_filter - Written
/tmp/hsperfdata_root/3533 - 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
/tmp/hsperfdata_root/3533
Sandbox background — not the file
15The 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 15 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 host
cl-glcb907925.gcdn.co - VM host
a1672.dscr.akamai.net - VM host
eip-terr-na.cdp1.digicert.com.akahost.net - VM host
nexusrules.officeapps.live.com
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.
- 3fa125f45a04b4133547…57bc05Not checkedno saved verdict
- 2fd920aa53bf7f965fb6…8637e1Not checkedno saved verdict
- 5cdfde8abc904ed8bd38…31e787Not 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 22, 2026, 8:21 AM UTC
- SHA-256
c7bb475ffa76936407005cde0365d256eadaa6eafc9612529f61f1dabe7f9796- SHA-1
c6894a347309d96c41fbeb4bd117e1b920d1e67c- MD5
3ecc95aaed241b5816df1816049f0d2c
About this file
Anubis_Beta_0.9.9.1.jar is a JAR file of 23.8 MB.
- Type and size
- JAR · 23.8 MB
- Signer
- Not applicable
- First seen
- Oct 22, 2026On VirusTotal.
- Submitted by
- 3 distinct sourcesRarely seen: few people have submitted this exact file.
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
- ClamAVClean
- 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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
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?
What should I do if I already opened or ran Anubis_Beta_0.9.9.1.jar?
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.