File scan report
Verdict Safe
Is blackout-
None of the 65 antivirus engines that checked it flagged the JAR, and its completed sandbox run produced no malicious verdict despite several uncorroborated offensive-technique…
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Confirm the JAR came from the intended source before running it, especially because it is uncommon. Keep security protection enabled and use isolation if its origin 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 this JAR, including the major antivirus engines represented in the results. One completed sandbox run produced no malicious verdict; its offensive-technique mappings were not backed by an injection target, persistence artifact, hostile sample traffic, or confirmed harmful child.
The strongest evidence is the absence of detections across 75 engines, with 17 major antivirus engines reporting no detection. A completed sandbox run also returned no malicious verdict. It mapped T1055, T1543.002, and T1562.001, but recorded no injected process, persistence indicator, or registry modification to substantiate those higher-risk interpretations. The listed network contacts were explicitly attributed to sandbox background activity rather than the sample. No malware-specific YARA rules or repository match corroborate a threat, although limited prevalence and nine unclassified dropped files warrant ordinary caution.
What We Detected
No named malware family, malware-specific YARA rule, or malware-repository match was present.
Threat Behavior
One completed sandbox run produced no malicious verdict. It mapped T1055, T1543.002, and T1562.001, but did not identify an injected target process, persistence indicator, program markers, or registry change. The recorded domain and IP were explicitly marked as analysis-environment background traffic, not sample activity. Nine dropped files lack saved verdicts, so they are an evidence gap rather than proof of harm.
What To Do Now
Use the JAR only if it came from the expected project or distributor, and keep security software enabled. Because the file is uncommon and its dropped components are unclassified, testing it in an isolated environment is prudent when its source is uncertain.
Where this verdict could be wrong3 caveats
- The runtime mapping includes process injection, service installation, and impairment of defenses, although no injection target, persistence artifact, or malicious sandbox verdict corroborates those mappings.
- The file has been submitted by only three sources, limiting prevalence-based reassurance.
- Nine dropped files have no saved verdict, so their safety remains unverified.
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 reported a malicious or suspicious detection.
- All 17 major antivirus engines represented in the results reported no detection.
- The completed sandbox run issued no malicious verdict.
- The observed network entries were identified as analysis-environment background traffic.
- No malware-specific researcher rules or known malicious child were identified.
- The test run mapped possible process injection, service installation, and impairment of defenses without identifying a target or confirming persistence.
- The file has appeared from only three submitting sources.
- Nine dropped components do not have saved classifications.
6 sources checked · all complete. 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
Includes the sandbox verdicts, 16 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 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 13, 2026, 6:47 AM UTC
- SHA-256
6a5dec652bd7ecb55f175caa1e8add4a645859358ca5b967eae302db8a0f7298- SHA-1
2666665b29d090d3b881fb1d641340194a060bd4- MD5
687af779515d3c63ebee51d2106b767d
About this file
blackout-1.5.3.jar is a JAR file of 1.4 MB.
- Type and size
- JAR · 1.4 MB
- Signer
- Not applicable
- First seen
- Sep 9, 2026On VirusTotal.
- Submitted by
- 3 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is blackout-1.5.3.jar safe?
What is blackout-1.5.3.jar?
How many antivirus engines detected blackout-1.5.3.jar?
What is the SHA-256 hash of blackout-1.5.3.jar?
Is it safe to open or run blackout-1.5.3.jar?
How up to date is this analysis of blackout-1.5.3.jar?
Community
Member reviews and reports for this exact file hash.