Is FreeToken-Setup-win-x64.exe safe?
Unsigned installer triggers two low-trust engines and shows process-injection and LSASS access in sandbox.
Two low-trust engines flag the file while 73 others remain silent. Sandbox reports T1055 and LSASS access, yet no tier-1 consensus or malicious children exist. Similar imphash samples were previously rated suspicious.
326c29f20e0e8a2775…85fda20d0d5dfaRecommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Two low-trust engines flag the file while 73 others remain silent. Sandbox reports T1055 and LSASS access, yet no tier-1 consensus or malicious children exist. Similar imphash samples were previously rated suspicious.
The file is a one-day-old NSIS-based installer lacking any code signature. Only two low-trust engines report malicious, satisfying the low-trust-only FP pattern, yet the sandbox captured process-injection and LSASS reads that are atypical for benign installers. Five prior files sharing the same imphash were all flagged suspicious under the same mixed-signal rule. Medium prevalence and installer hints reduce confidence in a clean verdict but do not rise to tier-1 malicious consensus.
What We Detected
75-engine scan shows 2 low-trust detections (APEX, Trapmine) and 0 tier-1 flags. The binary is unsigned and uses NSIS; sandbox execution produced dropped NSIS temp files plus a final freetoken-desktop.exe. MITRE techniques T1055, T1134 and T1485 were recorded.
Threat Behavior
Process injection and LSASS memory access are present, but no C2 domains, persistence keys or malicious dropped children were observed. External intel (YARAify, CIRCL, MalwareBazaar) returned zero hits.
What To Do Now
Do not run the installer on production systems. Keep Windows Defender and other endpoint protection enabled. If the software is required, obtain it from an official source and verify its digital signature before execution.
Where this verdict could be wrong1 caveat
- Sandbox observed LSASS access but no persistence indicators or C2 domains; could be installer self-extraction noise.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero tier-1 detections
- No malicious dropped children
- Medium prevalence across 95 sources
- Unsigned executable
- Sandbox reports process injection and LSASS access
- Five similar imphash samples previously rated suspicious
Treat as untrusted; obtain the software from an official, signed distribution if needed and keep all security software active.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 23MITRE ATT&CK techniques
- 11spawned processes
- 0network contacts
- 23filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
FreeToken-Setup-win-x64.exe
326c29f20e0e8a2775fb02e19fde08015273d36d965ced536685fda20d0d5dfa
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\FreeToken-Setup-win-x64.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nsyD2F1.tmp
C:\Users\<USER>\AppData\Local\Temp\nsyD2F1.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nsnD34F.tmp\System.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- C:\Users\<USER>\AppData\Local\Temp\nsyD2F1.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsnD34F.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsnD34F.tmp\modern-header.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsnD34F.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsnD34F.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\<USER>\AppData\Local\Temp\nsv9413.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsl9473.tmp
- C:\Users\user\AppData\Local\Temp\nsp4713.tmp
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 1fbe5855f2aca08506e2…07abaaNever scannednever seen before
- 95acc9c51c083bfc2af7…feb3ddNever scannednever seen before
- 5cf939f2cb738d7f2b7d…776c0fNever scannednever seen before
- b1350f487692057c8ffd…551fc0Never scannednever seen before
- 9baee42d66f715bba878…b40256Never scannednever seen before
- 9ee54d739fd4c319b66e…b9b8d7Never scannednever seen before
- 8b4c47c4cf5e76ec57dd…90d37cNever scannednever seen before
- 4b4e044d870da9653b4c…61890aNever scannednever seen before
- 5ba143b5db4a87d32d6e…ad4709Never scannednever seen before
- ebfd44a23c5e83eda335…1abf42Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 2 / 75engines flagged
- 95sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
2 of 75 antivirus engines flagged the file, including APEX and Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 105 times from 95 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: FreeToken-Setup-win-x64.exe — 326c29f20e0e8a2775fb02e19fde08015273d36d965ced536685fda20d0d5dfa
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\FreeToken-Setup-win-x64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nsyD2F1.tmp — C:\Users\<USER>\AppData\Local\Temp\nsyD2F1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nsnD34F.tmp\System.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\Explorer.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
2 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- FreeToken-Setup-win-x64.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 5.6 MB
- Last analyzed
- Aug 24, 2026, 8:34 AM UTC
326c29f20e0e8a2775fb02e19fde08015273d36d965ced536685fda20d0d5dfaSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't install it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Download a fresh installer from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is FreeToken-Setup-win-x64.exe safe, or is it malware?
What is FreeToken-Setup-win-x64.exe?
How many antivirus engines detected FreeToken-Setup-win-x64.exe?
What should I do if I already installed FreeToken-Setup-win-x64.exe?
How do I remove FreeToken-Setup-win-x64.exe?
What is the SHA-256 hash of 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.
