File scan report
Verdict Safe
Is Freesm
None of the 55 antivirus engines that checked it flagged the archive, while one sandbox produced no malicious verdict despite several unconfirmed offensive-technique mappings.
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.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 55 flagged
- Flagged 0
- No detection 55
- No result 20
- Code signing Not applicable
- Test run Completed
- First seen 25d ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Several offensive MITRE mappings add caution, but they lack an identified injection target, concrete persistence evidence, or corroboration from malware-specific intelligence.
The strongest evidence is the absence of detections across 75 engines, including no major flags or independent malicious votes. One completed sandbox run produced no malicious verdict and attributed its only network contact to analysis-environment background traffic. The run mapped T1055, T1543.002, and T1562.001, but recorded no injected process, persistence indicator, or registry modification. Malware-specific YARA rules and the malware-repository lookup supplied no corroboration. Confidence is moderated because the ten extracted files have no saved verdicts and no complete contacted-host reputation result is available.
What We Detected
None of the 55 antivirus engines that checked it flagged the ZIP, and there were no major or independent malicious detections. Malware-specific rule matching and the malware-repository lookup also returned no supporting hit.
Threat Behavior
One sandbox run produced no malicious verdict. It mapped T1055, T1543.002, and T1562.001, but did not identify an injected target, a persistence indicator, or a registry change. The recorded IP connection was labeled as background traffic from the analysis environment rather than activity attributable to the sample. A complete host-reputation cross-check is unavailable.
What To Do Now
Obtain the archive from the project's official distribution channel and verify any published checksum before extraction. Keep security software enabled, and scan the extracted executables individually because all ten files it created currently lack saved verdicts.
Where this verdict could be wrong3 caveats
- The sandbox mapped process injection, service execution, and impairment-of-defenses techniques, which warrant caution even though no injection target, persistence indicator, or malicious sandbox verdict was recorded.
- All 10 extracted files it created lack saved verdicts, so their contents have not received conclusive child-level classification.
- No complete reputation cross-check is available for observed hosts.
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 55 antivirus engines that checked it flagged the archive.
- No major antivirus engines reported a detection.
- The completed sandbox run produced no malicious verdict.
- No malware-specific research rules or malware-repository record matched the hash.
- No injected process or persistence indicator was recorded.
- The sandbox mapped possible process injection, service execution, and impairment of defenses.
- The archive is recently observed and has only moderate distribution.
- Ten extracted files lack saved child-level verdicts.
- No complete reputation check is available for observed hosts.
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 our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 14sandbox rule tags
- 9spawned processes
- 0network contacts
- 40filesystem & mutex artifacts
Includes the sandbox verdicts, 14 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 55 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 12, 2026, 12:05 AM UTC
- SHA-256
5144071af96199f79a83539960797f832937ea74eba6e8568c7d96e922cc3682- SHA-1
04ca600bebd18bd4b84574c39608c5c9a36ce4fb- MD5
d388fe28e060727f47b807e0b0651f48
About this file
FreesmLauncher-Windows-MSVC-Portable-2.3.1.zip is a ZIP file of 25.6 MB.
- Type and size
- ZIP · 25.6 MB
- Signer
- Not applicable
- First seen
- Oct 1, 2026On VirusTotal.
- Submitted by
- 19 distinct sources
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 FreesmLauncher-Windows-MSVC-Portable-2.3.1.zip safe?
What is FreesmLauncher-Windows-MSVC-Portable-2.3.1.zip?
How many antivirus engines detected FreesmLauncher-Windows-MSVC-Portable-2.3.1.zip?
What is the SHA-256 hash of FreesmLauncher-Windows-MSVC-Portable-2.3.1.zip?
Is it safe to open or extract FreesmLauncher-Windows-MSVC-Portable-2.3.1.zip?
How up to date is this analysis of FreesmLauncher-Windows-MSVC-Portable-2.3.1.zip?
Community
Member reviews and reports for this exact file hash.