File scan report
Verdict Safe
Is Free
Only 2 of the 70 antivirus engines that checked it flagged this unsigned installer, both with generic assessments from less reliable detectors, while major antivirus engines…
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.
Install it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows 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
2 of 70 flagged
- Flagged 2
- No detection 68
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 2mo 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
APEX and Trapmine flagged the installer generically, but no major antivirus engines detected it and no malware family was identified. The sandbox summary recorded no high-risk technique or named injection target; the unsigned status warrants obtaining it from the project's official release channel.
Seventeen major antivirus engines, including BitDefender, ESET, Fortinet and Kaspersky, reported no detection, and there is no family consensus. The sandbox summary contains no high-risk techniques or named injection target; the mapping lacks the artefact needed to treat it as observed injection. The file is unsigned, which removes a useful publisher-authentication signal but does not corroborate the detections. Similar installer-built files were mostly assessed as benign, although those import-table matches are weak because they belong to different publishers.
What We Detected
APEX and Trapmine were the only 2 of the 70 antivirus engines that checked it to flag the installer.
Threat Behavior
The sandbox summary recorded no high-risk techniques, malicious verdict, network contact, persistence indicator, or named process targeted for injection. A T1055 mapping appeared without a target process, so it does not demonstrate that injection occurred. No complete contacted-host reputation result is available, though the run recorded no sample contacts to evaluate.
What To Do Now
The executable is unsigned, so confirm that its hash and download source match the project's official release channel before running it. Keep security software enabled and rescan if a newer signed build becomes available.
Where this verdict could be wrong3 caveats
- The executable is unsigned, so there is no verified publisher identity to anchor trust.
- APEX and Trapmine both produced generic malicious assessments, although neither named a malware family.
- The installer had 95 distinct submitters, but that level of distribution alone does not establish that it is benign.
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 2 of the 70 antivirus engines that checked it flagged the installer, and no major antivirus engines detected it.
- No engine identified a specific malware family.
- The sandbox summary recorded no high-risk technique or named injection target.
- The antivirus analysis did not identify packed or high-entropy executable code.
- No malicious file it created was identified.
- The Windows executable is unsigned, so its publisher cannot be authenticated through code signing.
- APEX and Trapmine produced generic malicious assessments.
- No complete contacted-host reputation check is available.
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- 23sandbox rule tags
- 2spawned processes
- 0network contacts
- 23filesystem & mutex artifacts
Includes 23 mapped techniques, every process, file, registry and network entry and 7 dropped files.
Show the technical evidenceChapter 04
Technical details
2 of the 70 antivirus engines that checked it flag it; no publisher signature.
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.
Engines that flagged it 2
The saved verdict treats these detections as likely false positives.
- APEXMalicious
- Trapminemalicious.moderate.ml.score
File fingerprint
- Last analyzed
- Aug 24, 2026, 8:34 AM UTC
- SHA-256
326c29f20e0e8a2775fb02e19fde08015273d36d965ced536685fda20d0d5dfa- SHA-1
94d6518aaf2fcbca23fbfc2459ab3104699006f8- MD5
13da2839e03a050afd75e9163a3c769b
About this file
FreeToken-Setup-win-x64.exe is a Win32 EXE file of 5.9 MB.
- Type and size
- Win32 EXE · 5.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 23, 2026On VirusTotal.
- Submitted by
- 95 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers 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 FreeToken-Setup-win-x64.exe safe?
What is FreeToken-Setup-win-x64.exe?
How many antivirus engines detected FreeToken-Setup-win-x64.exe?
What is the SHA-256 hash of FreeToken-Setup-win-x64.exe?
Is it safe to install FreeToken-Setup-win-x64.exe?
How up to date is this analysis of FreeToken-Setup-win-x64.exe?
Community
Member reviews and reports for this exact file hash.
