GridinSoft Threat Intelligence

luapkg.exe file report

Clean record File reputation report
MD5 1744e81cc6bd9e112ac78da4ff72466a
Latest seen 2023-03-03 23:43:41 (3 years ago)
First seen 2023-03-03 23:43:41 (3 years ago)
Size 490 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-03-03 23:43:41 (3 years ago); latest analysis 2023-03-03 23:43:41 (3 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft(R) Windows (R) 2000 Operating System.

Digital signature

Signed by Microsoft Corporation. ThreatInfo marks this publisher as trusted for this record.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

luapkg.exe is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft(R) Windows (R) 2000 Operating System. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2023-03-03 23:43:41 (3 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Microsoft(R) Windows (R) 2000 Operating System
Company Name: Microsoft Corporation
MD5: 1744e81cc6bd9e112ac78da4ff72466a
Size: 490 KB
First Published: 2023-03-03 23:43:41 (3 years ago)
Latest Published: 2023-03-03 23:43:41 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-03-03 23:43:41 (3 years ago)
Signed By: Microsoft Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%sysdrive%\joseph.mcginley-6-1-2016\documents\oldjamdocs

ThreatInfo has observed luapkg.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 10 100.0%

The most common operating system signal for luapkg.exe is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

luapkg.exe is identified as pe for 32-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x0000283d
Image base 0x01000000

PE Sections:

Sections 3
Raw data 494080

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 34304 bytes · 6.9% of section data
MD5 b57e610f21987a4936310f973a2c6adf
.data 1024 bytes · 0.2% of section data
MD5 a8800423228f9a86657c80297a8ce5f0
.rsrc 458752 bytes · 92.8% of section data
MD5 62fc2882672ca111ac1a1bffe7bfea32

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 1744e81cc6bd9e112ac78da4ff72466a.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.