GridinSoft Threat Intelligence

LICLUA.EXE file report

Clean record File reputation report
MD5 d3bfd7057e24ee190d71a2659aa8f371
Latest seen 2021-02-15 16:05:22 (5 years ago)
First seen 2021-02-15 16:05:22 (5 years ago)
Size 463 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-02-15 16:05:22 (5 years ago); latest analysis 2021-02-15 16:05:22 (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-02-15 16:05:22 (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: d3bfd7057e24ee190d71a2659aa8f371
Size: 463 KB
First Published: 2021-02-15 16:05:22 (5 years ago)
Latest Published: 2021-02-15 16:05:22 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-15 16:05:22 (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 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 0x0001da72
Image base 0x00400000

PE Sections:

Sections 5
Raw data 457216

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

.text 132608 bytes · 29.0% of section data
MD5 e5430407fa0ec866d2c2091861dba4aa
.rdata 141824 bytes · 31.0% of section data
MD5 f89696e9a5c59f9d5d99820f16c1cb4f
.data 9728 bytes · 2.1% of section data
MD5 31a53ec1b3341cb52f2334d41040f016
.rsrc 158208 bytes · 34.6% of section data
MD5 aa2701635f6d12cb6ee9f6010fe5bc60
.reloc 14848 bytes · 3.2% of section data
MD5 f1b6864633aaa530161f264b7ed06525

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