File scan report
Verdict Suspicious
Is Lua Tools- win- Setup. exe safe? Treat it as suspicious.
Unsigned LuaTools installer flagged by 2 of the 70 antivirus engines that checked it and two community malware pattern rules, while its observed behaviour resembles an ordinary…
Read the whole reasonShow less
Why Suspicious? 2 antivirus engines flag it, but no major engine agrees and a community rule for known malware matched it.
Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already installed it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
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 1mo ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Only 2 of the 70 antivirus engines that checked it flagged this unsigned installer, and none of the major antivirus engines did. Two community pattern rules for droppers and ransomware matched it, which keeps it from being cleared. In the sandbox runs it installed LuaTools into the user profile and checked GitHub for updates, without recorded injection or a malicious run result.
The detections are thin: a generic Kingsoft trojan label and a machine-learning score, with all 18 major antivirus engines silent. Two malware-specific community pattern rules matched, though, and they are not cancelled by other evidence because a mid-tier engine also flagged the file. Evidence from the test run shows an installer unpacking LuaTools 1.3.0, contacting the GitHub releases API and an analytics endpoint. No injected process or malicious sandbox result was recorded. The file is unsigned, so no publisher vouches for it, although it is widely submitted. Earlier installers with the same build fingerprint received the same mixed assessment.
What We Detected
2 of the 70 antivirus engines that checked it flagged this file: Kingsoft with a generic trojan label and Trapmine with a machine-learning score. None of the 18 major antivirus engines reported it. Two community pattern rules aimed at droppers and ransomware matched, alongside several generic capability rules. The installer carries no digital signature.
Threat Behavior
The sandbox runs show the installer unpacking LuaTools 1.3.0 into the user's AppData folder and launching it. The application queried the GitHub releases API for the LuaTools project and contacted an analytics endpoint. No process injection target, persistence entry or malicious sandbox result was recorded. Host reputation checks covered only part of the observed contacts.
What To Do Now
Only run this installer if you obtained it from the project's official release page and trust the tool's purpose. Keep your antivirus enabled. If you did not intend to install LuaTools, delete the file.
Where this verdict could be wrong3 caveats
- Activity in the test run looks like an ordinary self-updating installer: it unpacks the app into the user profile, checks GitHub for releases and sends analytics, with no recorded injection target or malicious run.
- The two malware-specific pattern rules are community-written and broad (one simply named for ransomware), so they may match benign strings in a large .NET bundle.
- None of the 18 major antivirus engines flagged the file, and it has been submitted by 765 different sources.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 18 major antivirus engines flagged the file.
- Observed activity in the test run matches a normal application installer with update checks against GitHub.
- No process injection target or malicious sandbox result was recorded.
- The file has been submitted by 765 different sources.
- The installer has no digital signature, so no publisher identity backs it.
- Two community malware pattern rules (dropper and ransomware) matched the file.
- A mid-tier engine labels it as a generic trojan.
- The file is relatively new, first seen on Aug 30, 2026.
6 sources checked · 5 complete · 1 partial. 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- 24sandbox rule tags
- 4spawned processes
- 5network contacts
- 21filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Downloaded a file during the test run.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
LuaTools-win-Setup.exe
9a52511f3041a58f366faff3376a3579799b91e357d8717ffd28d72d8417d3cb
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
LuaTools-win-Setup.exe
"C:\Users\<USER>\Desktop\LuaTools-win-Setup.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
LuaTools.exe
"C:\Users\<USER>\AppData\Local\LuaTools\current\LuaTools.exe" --veloapp-install 1.3.0
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
velopack.log
C:\Users\<USER>\AppData\Local\velopack\velopack.log
Test run - Evidence 5 of 7: Written fileSeen in the test run
.velopack_dir_test
C:\Users\<USER>\AppData\Local\LuaTools\.velopack_dir_test
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
104.21.52.64
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
140.82.112.5
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 24 mapped techniques, every process, file, registry and network entry and 9 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 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 2
- KingsoftWin32.Troj.Unknown.a
- Trapminemalicious.high.ml.score
File fingerprint
- Last analyzed
- Sep 1, 2026, 9:37 AM UTC
- SHA-256
9a52511f3041a58f366faff3376a3579799b91e357d8717ffd28d72d8417d3cb- SHA-1
9b987a409dd0192b95e1f611f664c050629ddaf9- MD5
0374fd68c6b23baca6cf02a03b1fe8d6
About this file
LuaTools-win-Setup.exe is a Win32 EXE file of 11.9 MB.
- Type and size
- Win32 EXE · 11.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 30, 2026On VirusTotal.
- Submitted by
- 765 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Verdict history
- Malicious
- Suspiciousafter 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), 15 matched signature rules, 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 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?
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.