GridinSoft Threat Intelligence

lip.exe file report

Clean record File reputation report
MD5 0aeb380674fee569103a4ca1ded26572
Latest seen 2025-05-27 23:01:00 (a year ago)
First seen 2025-05-27 23:01:00 (a year ago)
Size 893 KB
Publisher AVG Secure Search
Signed by AVG Technologies

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2025-05-27 23:01:00 (a year ago); latest analysis 2025-05-27 23:01:00 (a year ago).

Publisher context

Company metadata: AVG Secure Search. Product metadata: LowInteg Application.

Digital signature

Signed by AVG Technologies. 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.

lip.exe is a Windows file recorded in the ThreatInfo database. It is associated with LowInteg Application. The reported company name is AVG Secure Search. The current detection status is Clean, based on the latest analysis from 2025-05-27 23:01:00 (a year 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: LowInteg Application
Company Name: AVG Secure Search
MD5: 0aeb380674fee569103a4ca1ded26572
Size: 893 KB
First Published: 2025-05-27 23:01:00 (a year ago)
Latest Published: 2025-05-27 23:01:00 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2025-05-27 23:01:00 (a year ago)
Signed By: AVG Technologies
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.

%programfiles%

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

lip.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 0x0007edf4
Image base 0x00400000

PE Sections:

Sections 5
Raw data 904192

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

.text 664064 bytes · 73.4% of section data
MD5 21b6eac6aeef868c5567f1761608f28f
.rdata 164864 bytes · 18.2% of section data
MD5 53b84804237be2ede564641871177bf9
.data 11264 bytes · 1.2% of section data
MD5 8dcaceebf8920c0416130a3d37eeb1d1
.rsrc 1536 bytes · 0.2% of section data
MD5 32ce2ad2339518d681ee46257e27a6c9
.reloc 62464 bytes · 6.9% of section data
MD5 ea3f942cec37208a2cb5835ee77d308c

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 0aeb380674fee569103a4ca1ded26572.
  • 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.