Is LuaTools-win-Setup.exe safe?
Only one low-trust engine detected this unsigned installer, but LSASS targeting, process-injection mapping, and incomplete host checks warrant caution before execution.
The antivirus result strongly resembles a false positive: only Trapmine flagged the file, while all 17 tier-1 engines were silent. However, the completed sandbox run produced process-injection and LSASS-targeting signals, and host-reputation coverage was incomplete, so the installer should not be run without source and hash verification.
f6bd024595477dfce0…75891cf8066732Recommended 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.
The antivirus result strongly resembles a false positive: only Trapmine flagged the file, while all 17 tier-1 engines were silent. However, the completed sandbox run produced process-injection and LSASS-targeting signals, and host-reputation coverage was incomplete, so the installer should not be run without source and hash verification.
Only 1 of 75 engines flagged the sample, and that was Trapmine using a generic machine-learning label; no tier-1 engine detected it. That pattern ordinarily points strongly toward a false positive. However, one completed sandbox run mapped activity to T1055 and reported LSASS targeting, alongside other offensive-technique mappings, creating meaningful counter-evidence. No malicious sandbox verdict or malicious dropped child was recorded, and the installation paths resemble a Velopack-based application update. The executable is unsigned with no publisher history, while the host-reputation check covered only part of the observed contacts. Two imphash-related prior decisions were unfavorable, but neither had a signer co-match, so they remain supporting rather than decisive evidence.
What We Detected
Trapmine was the sole detector among 75 antivirus engines, using the generic label “malicious.high.ml.score.” No tier-1 engine flagged the sample, which makes an antivirus false positive more likely than a well-corroborated malware detection. The executable is unsigned and has no established signer history.
Threat Behavior
One completed sandbox run mapped activity to T1055, T1486, T1543, and T1562.001. A separate heuristic reported process activity targeting LSASS, which is particularly concerning because credential-dumping tools commonly access that process. At the same time, the sandbox issued no malicious verdict, found no persistence indicators, and none of 10 inspected dropped children was identified as malicious. no complete contacted-host reputation result was available: only two of six distinct observed IP/URL contacts were covered, and raw.githubusercontent.com was listed as suspicious.
What To Do Now
Do not run this copy until its SHA-256 hash is confirmed against the developer's official release listing. Keep endpoint protection enabled, obtain a fresh installer from the official project release channel, and test it in an isolated environment if the publisher provides no signed or hash-verified package.
Where this verdict could be wrong4 caveats
- Trapmine is the only detector among 75 engines, its label is generic, and all 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false, persistenceIndicators is empty, and droppedChildren.hasMaliciousChild=false across 10 inspected children.
- prevalence records 546 sources and 631 submissions despite the sample being only two days old, reducing the likelihood of a narrowly distributed payload.
- The observed GitHub API release request and Velopack installation paths are consistent with software installation or update activity, though they do not explain the LSASS-related signal.
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/75 engines detected the sample
- engines.tier1Malicious=0 across 17 tier-1 engines
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false across 10 inspected children
- Prevalence shows 546 sources and 631 submissions
- Unsigned Win32 executable with no signer history
- Sandbox heuristic reported LSASS-targeting activity
- MITRE T1055 process-injection mapping
- MITRE T1562.001 defense-impairment mapping
- Host-reputation coverage was incomplete
- One contacted host was listed as suspicious
Keep endpoint protection enabled and avoid executing this copy until its hash is verified through the project's official release channel. Prefer a newly downloaded, signed or publisher-hash-verified build.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 6 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 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
- 24MITRE ATT&CK techniques
- 11spawned processes
- 6network contacts
- 19filesystem & 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: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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
LuaTools-win-Setup.exe
f6bd024595477dfce071bdb5ba244f16f04beaddc610628be675891cf8066732
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.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
velopack.log
C:\Users\<USER>\AppData\Local\velopack\velopack.log
04Isolated runtime analysis - Written fileObserved
.velopack_dir_test
C:\Users\<USER>\AppData\Local\LuaTools\.velopack_dir_test
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
raw.githubusercontent.com
Saved reputation verdict: suspicious.
06Contacted-host cross-check - Contacted hostObserved
185.199.108.133
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 185.199.108.133
- 172.67.196.53
- 140.82.116.6
- 162.159.36.2
- https://raw.githubusercontent.com/jsnli/steamappidlist/master/data/hardware_appid.json
- https://api.github.com/repos/madoiscool/LTSP/releases/latest
- C:\Users\<USER>\AppData\Local\velopack\velopack.log
- C:\Users\<USER>\AppData\Local\LuaTools\.velopack_dir_test
- C:\Users\<USER>\AppData\Local\LuaTools\packages\.velopack_lock
- C:\Users\<USER>\AppData\Local\LuaTools\Update.exe
- C:\Users\<USER>\AppData\Local\LuaTools\LuaTools.exe
- C:\Users\<USER>\AppData\Roaming\LuaToolsGui\cache.json.tmp
- cversions.3.m
- LuaToolsGui.SingleInstance
- Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 28e66bf0d21fce9b1b78…be98a8Never scannednever seen before
- 0732452a71e6c43c2ee8…942e06Never scannednever seen before
- f504e30e37a74936ac14…5cb9cfNever scannednever seen before
- da99caf3f45759da582e…94e2daNever scannednever seen before
- 4cbf03bb0c332dafdaa3…5b6c6eNever scannednever seen before
- da3f122d19f811a0ee68…fde700Never scannednever seen before
- b716430004afd2c1d2b8…3a468cNever scannednever seen before
- f7f7da311131ba2c387d…99a54aNever scannednever seen before
- 4ad4a3b2bed7f5f293f8…4f47aaNever scannednever seen before
- 32ad11116a15f7f52fc1…0bc539Never scannednever seen before
Servers this file contacts
This file contacts 1 host we've flagged suspicious in our own URL scanner.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 1 / 75engines flagged
- 546sources 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
1 of 75 antivirus engines flagged the file, including Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 631 times from 546 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: LuaTools-win-Setup.exe — f6bd024595477dfce071bdb5ba244f16f04beaddc610628be675891cf8066732
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: velopack.log — C:\Users\<USER>\AppData\Local\velopack\velopack.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: .velopack_dir_test — C:\Users\<USER>\AppData\Local\LuaTools\.velopack_dir_test
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: raw.githubusercontent.com — Saved reputation verdict: suspicious.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: 185.199.108.133 — Contact observed during runtime.
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.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence185.199.108.133 · 172.67.196.53 · 140.82.116.6
1 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- LuaTools-win-Setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 11.3 MB
- Last analyzed
- Sep 11, 2026, 9:43 AM UTC
f6bd024595477dfce071bdb5ba244f16f04beaddc610628be675891cf8066732Safety & 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 LuaTools-win-Setup.exe safe, or is it malware?
What is LuaTools-win-Setup.exe?
How many antivirus engines detected LuaTools-win-Setup.exe?
What should I do if I already installed LuaTools-win-Setup.exe?
How do I remove LuaTools-win-Setup.exe?
What is the SHA-256 hash of LuaTools-win-Setup.exe?
How up to date is this analysis of LuaTools-win-Setup.exe?
Community
Member reviews and reports for this exact file hash.