File scan report
Verdict Safe
Is Tenkaichi3
Only MaxSecure flagged this archive with a generic label, while 18 major antivirus engines and the available evidence from the test run supplied no corroborating threat indicators.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Open it only if you trust the person or website you got it from.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
1 of 67 flagged
- Flagged 1
- No detection 66
- No result 8
- Code signing Not applicable
- Test run Completed
- First seen 10d ago
Chapter 02
Why we think so
2 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Only 1 of the 67 antivirus engines that checked it flagged the archive, and that result came from less reliable MaxSecure using a generic label. The major antivirus engines were silent, while observed execution showed no malicious sandbox assessment, named injection target, hostile contacted host, or malicious dropped component.
The sole detection among 75 engines came from MaxSecure and used a generic trojan label rather than a recognized malware family. The sandbox runs recorded no malicious assessment or high-risk technique backed by a concrete artifact. Although was mapped, no target process was identified, so it does not establish process injection. Reputation checks covered all four listed domains without finding a known hostile host, and no inspected child carried a malicious determination. The file is recently observed, but that limited history does not outweigh the strong less reliable-only false-positive pattern.
What We Detected
Only 1 of the 67 antivirus engines that checked it flagged the archive. MaxSecure supplied a generic trojan label, while none of the 18 reporting major antivirus engines produced a detection and no recognized malware family was identified.
Threat Behavior
The sandbox runs did not return a malicious assessment. T1055 was mapped, but no target process was recorded, so the evidence does not show actual process injection. All four listed domains were covered by the available reputation check without a known hostile result, and no inspected dropped component had a malicious determination.
What To Do Now
The isolated generic detection is most consistent with a false positive. Obtain the archive from the project's official release channel, keep security software enabled, and rescan if the contents or hash differ from the expected download.
Where this verdict could be wrong2 caveats
- MaxSecure reported a generic Trojan.Malware.300983.susgen detection.
- The archive was first observed on Oct 15, 2026, so its longer-term reputation is not yet established.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of the 67 antivirus engines that checked it flagged the archive, and the detector was less reliable.
- None of the 18 reporting major antivirus engines produced a detection.
- Observed execution received no malicious sandbox assessment and identified no concrete process-injection target.
- The reputation check covered all four listed domains without finding a known hostile host.
- No inspected dropped component had a malicious determination.
- MaxSecure reported a generic trojan detection.
- The archive was first observed on Oct 15, 2026, leaving limited long-term reputation.
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- 8sandbox rule tags
- 5spawned processes
- 2network contacts
- 15filesystem & mutex artifacts
Includes the sandbox verdicts, 8 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 67 antivirus engines that checked it flags 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.
Engines that flagged it 1
The saved verdict treats these detections as likely false positives.
- MaxSecureTrojan.Malware.300983.susgen
File fingerprint
- Last analyzed
- Oct 15, 2026, 11:19 PM UTC
- SHA-256
6ca44348b488a558d24ddad18c5a5b2710ef20284326117192d68b9932a69206- SHA-1
7092142a95d5eabf635ae84ffc7bd50dbef88581- MD5
a7c489d263bd3beae1117b479e7f59e4
About this file
Tenkaichi3Decomp-windows-x64.zip is a ZIP file of 9.3 MB.
- Type and size
- ZIP · 9.3 MB
- Signer
- Not applicable
- First seen
- Oct 15, 2026On VirusTotal.
- Submitted by
- 16 distinct sources
First scanned Updated
Verdict history
- Not fully confirmed
- Safeafter the analysis was completed
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
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 Tenkaichi3Decomp-windows-x64.zip safe?
What is Tenkaichi3Decomp-windows-x64.zip?
How many antivirus engines detected Tenkaichi3Decomp-windows-x64.zip?
What is the SHA-256 hash of Tenkaichi3Decomp-windows-x64.zip?
Is it safe to open or extract Tenkaichi3Decomp-windows-x64.zip?
How up to date is this analysis of Tenkaichi3Decomp-windows-x64.zip?
Community
Member reviews and reports for this exact file hash.