GridinSoft Threat Intelligence

LICLUA.EXE file report

Clean record File reputation report
MD5 f460127eec2b245ba9476937ace893cb
Latest seen 2021-01-12 17:25:20 (5 years ago)
First seen 2020-08-20 21:21:21 (5 years ago)
Size 474 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-08-20 21:21:21 (5 years ago); latest analysis 2021-01-12 17:25:20 (5 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-01-12 17:25:20 (5 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: f460127eec2b245ba9476937ace893cb
Size: 474 KB
First Published: 2020-08-20 21:21:21 (5 years ago)
Latest Published: 2021-01-12 17:25:20 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 17:25:20 (5 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 80.0%
Windows 8.1 20.0%

The most common operating system signal for LICLUA.EXE is Windows 10 with 80.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 0x0001e151
Image base 0x00400000

PE Sections:

Sections 5
Raw data 466944

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

.text 135680 bytes · 29.1% of section data
MD5 245ffb6be5828b77aacf264c6afe9a46
.rdata 147968 bytes · 31.7% of section data
MD5 45f6f1749fe9424a4ad7ea8372b9cad5
.data 9728 bytes · 2.1% of section data
MD5 ee1e2f9ea0eb63561b9102189418406a
.rsrc 158208 bytes · 33.9% of section data
MD5 ec86c60bff6cc1fce5ee56463338fd68
.reloc 15360 bytes · 3.3% of section data
MD5 bc5175ef0973b672d02522d0a55c0754

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 f460127eec2b245ba9476937ace893cb.
  • 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.