Is LuaTools-win-Setup.exe safe?
Unsigned installer shows process-injection and LSASS-access behaviour with only one tier-1 detection.
One tier-1 engine flags the file as DangerousObject while 16 tier-1 engines remain silent. Sandbox evidence of process injection and LSASS access raises concern, yet the file is widely submitted and lacks corroborating external-intel hits.
f14d9071ec8ad59f2f…9b44b1c6e805f7Recommended 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.
One tier-1 engine flags the file as DangerousObject while 16 tier-1 engines remain silent. Sandbox evidence of process injection and LSASS access raises concern, yet the file is widely submitted and lacks corroborating external-intel hits.
The sample is unsigned and exhibits four offensive MITRE techniques, including process injection and LSASS access, which legitimate installers rarely perform. Only a single tier-1 engine (Kaspersky) reports malicious, and the family consensus is weak. Prevalence is high for a two-day-old file, and no YARA or MalwareBazaar hits exist. Contacted-host reputation is incomplete, leaving the direct-IP traffic inconclusive. These mixed signals place the file in the suspicious category.
What We Detected
Three of 75 engines flagged the sample; Kaspersky (tier-1) labelled it UDS:DangerousObject.Multi.Generic. Sandbox execution recorded process injection (T1055), data encryption (T1485), service creation (T1543), and defence-evasion (T1562.001). The installer wrote multiple files under AppData\Local\LuaTools and contacted six raw IP addresses plus raw.githubusercontent.com.
Threat Behavior
Observed LSASS memory access and direct-IP C2-style traffic are consistent with credential-dumping or backdoor tooling. No dropped child files were flagged malicious, and external-intel sources returned no matches.
What To Do Now
Do not execute the file on production systems. Keep endpoint protection enabled and monitor for additional indicators such as persistence mechanisms or outbound beaconing before deciding on removal or further analysis.
Where this verdict could be wrong3 caveats
- engines.tier1Malicious only 1/17 tier-1 engines; 16 tier-1 engines reported clean.
- prevalence 512 submissions across 433 sources suggests wider distribution than typical malware campaigns.
- YARAify returned 0 rules and MalwareBazaar has no family match.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 16 of 17 tier-1 engines reported clean
- Widely submitted (433 sources) within two days
- No YARAify, CIRCL, or MalwareBazaar hits
- Unsigned executable claiming to be an installer
- Sandbox observed LSASS access and process injection
- Direct-IP network traffic with one suspicious contacted host
Treat the file as untrusted; run it only in an isolated environment or obtain a signed build from the vendor before broader deployment.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 9 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
- 9network contacts
- 20filesystem & 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
f14d9071ec8ad59f2f292ae957e54e4dc76e8c0d3a4cd750919b44b1c6e805f7
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
172.67.196.53
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.
- 172.67.196.53
- 140.82.114.6
- 185.199.110.133
- 162.159.36.2
- 184.25.59.26
- 20.60.81.165
- https://raw.githubusercontent.com/jsnli/steamappidlist/master/data/hardware_appid.json
- https://analytics.lua.tools/api/send
- 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\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- 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.
- 0234c4b3f819b8f9f234…81be85Never 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
- f8f0c2f374eaee48f07a…c566fcNever scannednever seen before
- fd0bd749be67a3468dd6…eb198cNever scannednever seen before
- f3f71fa25be13b1957e8…735e77Never scannednever seen before
- 338ae3cc43677c0be2ea…c27dceNever 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
- 3 / 75engines flagged
- 433sources 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
3 of 75 antivirus engines flagged the file, including Gridinsoft and Kaspersky.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 512 times from 433 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: LuaTools-win-Setup.exe — f14d9071ec8ad59f2f292ae957e54e4dc76e8c0d3a4cd750919b44b1c6e805f7
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: 172.67.196.53 — 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.
Evidence172.67.196.53 · 140.82.114.6 · 185.199.110.133
3 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.2 MB
- Last analyzed
- Aug 15, 2026, 5:13 PM UTC
f14d9071ec8ad59f2f292ae957e54e4dc76e8c0d3a4cd750919b44b1c6e805f7Safety & 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.