File scan report
Verdict Safe
Is lua54. dll safe? Yes, no threats found.
None of the 70 antivirus engines that checked it flagged this 64-bit Lua DLL, it has been submitted by 331 sources since 2021, and its sandbox runs were clean.
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
No action is needed. Download libraries from their official project source and keep your antivirus enabled.
Good practice2 tips
We found nothing harmful in this file.
Use it only as part of a program you got from the developer's own website.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 5y ago
Chapter 02
Why we think so
1 point against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
It has been seen from 331 distinct submitters since first seen on Jan 16, 2021. No hostile network contacts or injection targets were recorded.
0 of the 70 antivirus engines that checked it flagged the file, including 17 major antivirus engines that reported clean. It is widely submitted, with 331 submitters since first seen on Jan 16, 2021. Four sandbox runs gave a combined clean verdict with no named injection target. No malware-specific rules or public database listings exist. The lack of a signature is the only minor gap.
What We Detected
No engine flagged this Win32 DLL. It has a normal structure with no packing or high-entropy code.Threat Behavior
The sandbox runs were clean and the contacted hosts were only the analysis VM's background traffic.What To Do Now
No action is needed. Obtain it from the original project source and keep protection enabled.Where this verdict could be wrong1 caveat
- The DLL is unsigned, so there is no publisher identity to confirm the build is the genuine Lua library.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No engine among 75 flagged it
- Submitted by 331 distinct sources since 2021
- Combined sandbox verdict was clean
- No malware-specific rules or database listings
- The file is unsigned, so its publisher cannot be verified.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 4 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 4isolated sandbox runs
- 13sandbox rule tags
- 1spawned processes
- 0network contacts
- 40filesystem & mutex artifacts
What this file did when executed
This file was detonated in 4 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
13MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1018
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1055· Process injection
- T1057· Lists programs
- T1071· Application protocol
- T1082· System recon
- T1095· Custom network
- T1129· Loads modules
- T1218.011
- T1497· Sandbox evasion
- T1518.001· Checks your AV
Observed activity
Processes started
1Programs the file ran, with their command lines.
rundll32.exe"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\init.dll",#1
Files
30Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\112c75da-be6d-43a7-988a-2ae53558cf91 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\6f4fc23e-b684-4133-bd11-365924de7d41 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\7464b618-8136-4c4b-ab48-f3080a35d506
Show all 30 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp\13886ec0-7fbc-4b60-abf5-985b66dc88de - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\2e94676a-f2a0-4246-986f-b1ed49eb0891 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\fca8f295-cf6a-4bd8-989e-309617034d44 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E74.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER53C4.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER55AA.tmp.xml - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_lua_30dc1112d22a8a3915c96d75a8eb934e41c8dc6_c2285d6f_04cbd170 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_lua_30dc1112d22a8a3915c96d75a8eb934e41c8dc6_c2285d6f_04cbd170\Report.wer - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_lua_30dc1112d22a8a3915c96d75a8eb934e41c8dc6_c2285d6f_0c9be2f5 - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E74.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER53C4.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER55AA.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E74.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER53C4.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER55AA.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.Window_dc7c09b5b22497c66105fec8cf4793ba24a83ae_676f2386_15d6973b - Deleted
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.Window_dc7c09b5b22497c66105fec8cf4793ba24a83ae_676f2386_15d6973b\Report.wer - Deleted
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.Window_dc7c09b5b22497c66105fec8cf4793ba24a83ae_676f2386_172deaf8 - Deleted
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.Window_dc7c09b5b22497c66105fec8cf4793ba24a83ae_676f2386_172deaf8\Report.wer - Deleted
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.Window_dc7c09b5b22497c66105fec8cf4793ba24a83ae_676f2386_174f43cc - Deleted
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.Window_dc7c09b5b22497c66105fec8cf4793ba24a83ae_676f2386_174f43cc\Report.wer - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E01.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E01.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER8313.tmp
Registry and auto-start
15Settings the file changed, including ways to start again after a restart.
- Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\WritePermissionsCheck - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\ProgramId - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\FileId - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\LowerCaseLongPath - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\LongPathHash - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\Name
Show all 15 entries for registry and auto-start
- Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\OriginalFileName - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\Publisher - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\Version - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\BinFileVersion - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\BinaryType - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\ProductName - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\ProductVersion - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\LinkDate - Set
\REGISTRY\A\{57e58bab-7551-749f-7579-2204c5988604}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\BinProductVersion
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
Local\WERReportingForProcess3220Global\AmiProviderMutex_InventoryApplicationFileGlobal\8c0575a4-80f6-4bcd-bbb7-c01dfa5c1cf7\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6444\Sessions\1\BaseNamedObjects\Global\f03d8800-8cd6-4172-bea0-0c00617cfd1a\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6424
Show all 10 entries for mutexes
\Sessions\1\BaseNamedObjects\Global\9225c918-90ef-48c5-822c-b41ee16afd2b\Sessions\1\BaseNamedObjects\Global\daf7b180-5425-4ae0-8538-082d7907dfe9\Sessions\1\BaseNamedObjects\Global\78b451ea-45e3-4337-86ae-b3c14f0f4214\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess4332
Sandbox background — not the file
7The analysis machine's own processes and connections, recorded in every run.
- VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 3220 -s 540 - VM host
245.50.188.52.in-addr.arpa - VM host
fp2E7A.wpc.2BE4.phicdn.net - VM host
49.28.101.95.in-addr.arpa - VM host
fp2e7a.wpc.phicdn.net - VM host
154.210.82.20.in-addr.arpa
Show all 7 entries for sandbox background — not the file
- VM host
61.234.212.23.in-addr.arpa
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 2114966cd92f2c0756c3…7e81c0Not checkedno saved verdict
- c2d20b876309b5a7a164…2f35acNot checkedno saved verdict
- 511bec6a461faf1df5f9…feb402Not checkedno saved verdict
- 4a0b72c15aa79e7612a1…a9cb0bNot checkedno saved verdict
- 35622f12eec93df19720…bfddc5Not checkedno saved verdict
- 6e7f007a7c20bd92f08a…1fd399Not checkedno saved verdict
- 29378d9649e121f8b9f0…892389Not checkedno saved verdict
- 98f0297bf122de985753…c97518Not checkedno saved verdict
- 65bffd02710701f7633e…aac556Not checkedno saved verdict
- 6a18b1dbfb89e168609d…5b8d8bNot checkedno saved verdict
Chapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 24, 2026, 9:19 PM UTC
- SHA-256
0fe22c4f44465370bc44dcf47370052edf19a006b1ccc3f36a19ee30eff20955- SHA-1
95da0c62c06417cc1e699e8a9861079aaa83f669- MD5
381cb8b617adb5c253a4f7a1dc368f47
About this file
lua54.dll is a Win32 DLL file of 356.2 kB.
- Type and size
- Win32 DLL · 356.2 kB
- Signer
- UnsignedNo code signature.
- First seen
- Jan 16, 2021On VirusTotal.
- Submitted by
- 331 distinct sources
- Packer
- None detected
- Entropy
- 5.96 of 8
First scanned
Antivirus consensus
0 of 70 engines flagged this file
5 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines0flagged
- Tier-236 engines0flagged
- Low-trust17 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is lua54.dll safe?
What is lua54.dll?
How many antivirus engines detected lua54.dll?
What is the SHA-256 hash of lua54.dll?
Is it safe to use lua54.dll?
How up to date is this analysis of lua54.dll?
Community
Member reviews and reports for this exact file hash.