Is LuaTools-win-Setup.exe safe?
Only one low-trust engine detected this unsigned installer, but recorded process-injection, defense-evasion, and LSASS-related activity warrants caution pending publisher verification.
The antivirus pattern strongly resembles a false positive: only Trapmine flagged the file, and no tier-1 engine detected it. However, the unsigned installer produced process-injection, defense-evasion, and LSASS-related evidence during one runtime analysis, so it should not be trusted without confirming its source and publisher.
bae35a2c7fb871adf5…6d57cddf58ee8fRecommended 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 pattern strongly resembles a false positive: only Trapmine flagged the file, and no tier-1 engine detected it. However, the unsigned installer produced process-injection, defense-evasion, and LSASS-related evidence during one runtime analysis, so it should not be trusted without confirming its source and publisher.
Only 1 of 75 engines flagged the sample, and that alert came from Trapmine with a generic machine-learning label; no tier-1 engine detected it. This low-trust-only pattern substantially raises the chance of a false positive. However, one completed runtime analysis recorded T1055 process injection, T1562.001 defense impairment, and activity involving LSASS, which are significant counter-signals even though the sandbox itself returned a clean assessment. The installer is unsigned and has no established publisher history, while one fully checked contacted domain had a suspicious cached reputation. no complete contacted-host reputation result was available, malicious dropped child, named family consensus, or external intelligence match independently corroborates malware, leaving materially mixed evidence.
What We Detected
Trapmine was the only engine to flag the file among 75 engines, using the generic label “malicious.high.ml.score.” No tier-1 engine reported a detection, and there was no named-family consensus. The executable is unsigned and lacks historical signer data, so its publisher identity cannot be authenticated.
Threat Behavior
One completed runtime observation recorded four offensive techniques: T1055 process injection, T1485 data destruction, T1543 service modification, and T1562.001 defense impairment. A separate heuristic associated process activity with LSASS, which can indicate credential-access behavior, although the saved evidence does not prove credential theft. The runtime system returned a clean assessment, all four contacted domains received reputation coverage, and none was known malicious; raw.githubusercontent.com had a suspicious cached rating. Ten dropped files were inspected without a malicious child finding, but their individual verdicts remained unknown.
What To Do Now
Verify that the SHA-256 bae35a2c7fb871adf5aec2a4f8bade951533a1fb8672b273986d57cddf58ee8f came directly from the project's official release channel before running it. Keep endpoint protection enabled and avoid executing the installer on a production or sensitive system until the publisher or additional independent analysis explains the injection and LSASS-related activity.
Where this verdict could be wrong5 caveats
- The sole antivirus alert is Trapmine's generic low-trust label, while 15 tier-1 engines reported no detection.
- behaviour.sandboxVerdicts[0].verdict='clean' and behaviour.hasMaliciousSandboxVerdict=false, although the recorded MITRE and LSASS-related activity remains concerning.
- droppedChildren.hasMaliciousChild=false, but all 10 child verdicts are unknown rather than affirmatively benign.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false provide no independent family corroboration.
- prevalence.uniqueSources=1244 indicates broad distribution despite the file being only four days old.
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 file, and the sole alert was low-trust
- engines.tier1Malicious=0 with 15 tier-1 engines reporting no detection
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false across 10 inspected children
- MalwareBazaar, CIRCL, and YARAify returned no corroborating hit
- Unsigned Windows executable with no established signer history
- Runtime evidence mapped to T1055 process injection
- Runtime evidence mapped to T1562.001 defense impairment
- Heuristic evidence references activity targeting lsass.exe
- contactedHosts identified raw.githubusercontent.com as suspicious
- File reputation is -11 and the sample was first submitted four days ago
Obtain the installer only from the project's verified official release channel and compare its SHA-256 before use. Keep antivirus and endpoint protection enabled, and quarantine the file if its source cannot be authenticated.
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
Partial4 of 8 contacted hosts were cross-checked; coverage is incomplete.
YARA
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
- 25MITRE ATT&CK techniques
- 13spawned processes
- 11network contacts
- 22filesystem & 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: 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.
Moderate concern: Runs hidden system commands (script or shell).
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
bae35a2c7fb871adf5aec2a4f8bade951533a1fb8672b273986d57cddf58ee8f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\LuaTools-win-Setup.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
analytics.lua.tools
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.
- raw.githubusercontent.com
- analytics.lua.tools
- api.github.com
- dotnetcli.blob.core.windows.net
- 104.21.52.64
- 185.199.110.133
- 140.82.114.6
- 162.159.36.2
- https://analytics.lua.tools/api/send
- https://api.github.com/repos/madoiscool/LTSP/releases/latest
- https://raw.githubusercontent.com/jsnli/steamappidlist/master/data/hardware_appid.json
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\LuaTools\DisplayIcon
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\LuaTools\DisplayName
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\LuaTools\DisplayVersion
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\LuaTools\InstallDate
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\LuaTools\InstallLocation
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\LuaTools\Publisher
- 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\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\<USER>\AppData\Roaming\LuaToolsGui\cache.json.tmp
- cversions.3.m
- LuaToolsGui.SingleInstance
- Local\SessionImmersiveColorMutex
- 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.
- ddc654cf2846c917a313…95ed63Never scannednever seen before
- 28e66bf0d21fce9b1b78…be98a8Never scannednever seen before
- f504e30e37a74936ac14…5cb9cfNever scannednever seen before
- 4cbf03bb0c332dafdaa3…5b6c6eNever scannednever seen before
- da3f122d19f811a0ee68…fde700Never scannednever seen before
- b716430004afd2c1d2b8…3a468cNever scannednever seen before
- 4ad4a3b2bed7f5f293f8…4f47aaNever scannednever seen before
- 1b0e33c0c00629f909e0…b91223Never scannednever seen before
- 548ec6279f56aaf7b547…a3d11eNever scannednever seen before
- 866f8c3dc8fd95def902…0f7b18Never 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.
- 2rule hits recorded
- 1 / 75engines flagged
- 1,244sources 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 1,439 times from 1,244 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: LuaTools-win-Setup.exe — bae35a2c7fb871adf5aec2a4f8bade951533a1fb8672b273986d57cddf58ee8f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\LuaTools-win-Setup.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: analytics.lua.tools — 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.exe
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 29, 2026, 1:11 PM UTC
bae35a2c7fb871adf5aec2a4f8bade951533a1fb8672b273986d57cddf58ee8fSafety & 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?
I already downloaded and installed LuaTools-win-Setup.exe — what should I do?
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.