GridinSoft Threat Intelligence

LICLUA.EXE file report

Clean record File reputation report
MD5 be9c0417cc3cdf9d3891d1fb2274a305
Latest seen 2021-11-21 21:37:39 (4 years ago)
First seen 2021-11-21 21:37:39 (4 years ago)
Size 477 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-11-21 21:37:39 (4 years ago); latest analysis 2021-11-21 21:37:39 (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-11-21 21:37:39 (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: be9c0417cc3cdf9d3891d1fb2274a305
Size: 477 KB
First Published: 2021-11-21 21:37:39 (4 years ago)
Latest Published: 2021-11-21 21:37:39 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-11-21 21:37:39 (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 0x0001dae3
Image base 0x00400000

PE Sections:

Sections 5
Raw data 470528

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

.text 130560 bytes · 27.7% of section data
MD5 5045be49eb4ea28e09d2f470ce755250
.rdata 158720 bytes · 33.7% of section data
MD5 41f7ba0a0950df25fc208f6ccbcd7f19
.data 9216 bytes · 2.0% of section data
MD5 071fdd6bbf8af701c44b2be53b77f30f
.rsrc 157184 bytes · 33.4% of section data
MD5 70d8d8d310ecd417d61bf642ce146f88
.reloc 14848 bytes · 3.2% of section data
MD5 7fb7c704a4538bd67ce573aa089530db

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