GridinSoft Threat Intelligence

LICLUA.EXE file report

Clean record File reputation report
MD5 255afee663e14a06ac75cad27a2c20d2
Latest seen 2021-10-20 20:46:37 (4 years ago)
First seen 2020-08-27 09:48:38 (5 years ago)
Size 472 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-08-27 09:48:38 (5 years ago); latest analysis 2021-10-20 20:46:37 (4 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Office Licensing Admin Access Provider.

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.

LICLUA.EXE is a Windows file recorded in the ThreatInfo database. It is associated with Office Licensing Admin Access Provider. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-10-20 20:46:37 (4 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: Office Licensing Admin Access Provider
Company Name: Microsoft Corporation
MD5: 255afee663e14a06ac75cad27a2c20d2
Size: 472 KB
First Published: 2020-08-27 09:48:38 (5 years ago)
Latest Published: 2021-10-20 20:46:37 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-10-20 20:46:37 (4 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.

%commondir%\microsoft shared

ThreatInfo has observed LICLUA.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 LICLUA.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.

LICLUA.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 0x0001deae
Image base 0x00400000

PE Sections:

Sections 5
Raw data 464896

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

.text 135168 bytes · 29.1% of section data
MD5 23e72f0ca109c72d75b089dc6be995a7
.rdata 146432 bytes · 31.5% of section data
MD5 988a05660f0b0519d804db5610fcff5b
.data 9728 bytes · 2.1% of section data
MD5 4415e292b8e9ec97d8e8ca1e35591b9e
.rsrc 158208 bytes · 34.0% of section data
MD5 51caa729c5ff2dfd97c73c867e629e9e
.reloc 15360 bytes · 3.3% of section data
MD5 1e29335c5e35bc395fcfd6cb70a1258c

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 255afee663e14a06ac75cad27a2c20d2.
  • 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.