File scan report
Verdict Safe
Is invincible-
This Java archive was flagged by none of the 63 antivirus engines that checked it, and sandbox runs showed only ordinary Java activity with no high-risk techniques.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
The file shows no signs of malicious behaviour; obtain it from its official distribution page and keep your security software enabled.
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 63 flagged
- Flagged 0
- No detection 63
- No result 12
- Code signing Not applicable
- Test run Completed
- First seen 4d ago
Chapter 02
Why we think so
1 point against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Sandbox runs launched it in the normal Java runtime with no network contacts, no persistence and no high-risk techniques. It is very new and rarely seen, so some caution about its source still applies.
None of the 63 antivirus engines that checked it flagged this JAR file, and every major antivirus engine reported it clean. Two sandbox runs executed it through the standard Java runtime, recorded no network contacts, no persistence and no registry changes, and the recorded sandbox verdict was clean. Public malware databases and community rule sets returned no matches. The main limitation is that the file is and has been submitted only once.
What We Detected
No detections from any of the 75 engines, including all major antivirus engines. No matches in public malware databases or community malware rules.
Threat Behavior
The sandbox runs started the archive with the Java runtime on Windows and Linux. Only Java's usual temporary performance files were written; no network connections, persistence mechanisms or registry changes were recorded. Checks for a debugging environment and CPU name are common in Java programs and games.
What To Do Now
The file appears to be an ordinary Java application or game mod. Download it only from the project's official page, and keep your antivirus protection enabled.
Where this verdict could be wrong2 caveats
- The file is and has been seen from only one submitter, so the engines have had little time to build detections for it.
- The sandbox tags note the program checks for a debugging environment and the CPU name, which some malware does, although Java runtimes and games commonly do the same.
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 63 antivirus engines that checked it flagged the file, including all major antivirus engines.
- Sandbox runs showed only normal Java activity in the test run with no network contacts or persistence.
- No matches in public malware databases or community malware rules.
- The file is and has been seen from only one submitter.
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 2 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 2isolated sandbox runs
- 14sandbox rule tags
- 2spawned processes
- 0network contacts
- 5filesystem & mutex artifacts
What this file did when executed
This file was detonated in 2 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
14MITRE 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
- T1074
- T1082· System recon
- T1105· Network file transfer
- T1106
- T1129· Loads modules
- T1202
- T1518.001· Checks your AV
- T1564· Hides artifacts
- T1564.001· Hides artifacts
- T1564.003· Hides artifacts
- T1574· Execution hijack
Observed activity
Processes started
2Programs 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"java/usr/bin/java -jar /tmp/runtime.jar
Files
5Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\556 - Written
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp - Written
/proc/3537/coredump_filter - Written
/tmp/hsperfdata_root/3537 - Deleted
/tmp/hsperfdata_root/3537
Sandbox background — not the file
1The 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
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache. 2 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 6b88ccf776257a48da57…ef7f7bNot checkedno saved verdict
- 4ceaba26b59326e13507…cc8f98Not checkedno saved verdict
Chapter 04
Technical details
None of the 63 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 21, 2026, 8:14 PM UTC
- SHA-256
89495972b6b08b5aa84cc0a6d561b421295c4ad31ab8f8b574a3e3e51de3613b- SHA-1
a41bdb5ff6e9a5519d006dd884663b4652bb18ea- MD5
61e28d38ac3d95b07f87d461ae7aa5ad
About this file
invincible-machine-gun-1.0.jar is a JAR file of 792.4 kB.
- Type and size
- JAR · 792.4 kB
- Signer
- Not applicable
- First seen
- Oct 21, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Antivirus consensus
0 of 63 engines flagged this file
12 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-232 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
- GoogleNo result
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookClean
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaNo result
- 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 invincible-machine-gun-1.0.jar safe?
What is invincible-machine-gun-1.0.jar?
How many antivirus engines detected invincible-machine-gun-1.0.jar?
What is the SHA-256 hash of invincible-machine-gun-1.0.jar?
Is it safe to open or run invincible-machine-gun-1.0.jar?
How up to date is this analysis of invincible-machine-gun-1.0.jar?
Community
Member reviews and reports for this exact file hash.