GridinSoft Threat Intelligence

Lavasoft.AppCore.dll file report

Under review File reputation report
MD5 1aa8da2640e7f6ea8f7c0cdfc5f4024e
Latest seen 2025-05-21 23:01:25 (a year ago)
First seen 2020-07-01 20:22:41 (5 years ago)
Size 118 KB
Signed by Lavasoft Limited

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-07-01 20:22:41 (5 years ago); latest analysis 2025-05-21 23:01:25 (a year ago).

Publisher context

Product metadata: Lavasoft.AppCore.

Digital signature

Signed by Lavasoft Limited. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

Lavasoft.AppCore.dll is a Windows file recorded in the ThreatInfo database. It is associated with Lavasoft.AppCore. The current detection status is Undefined, based on the latest analysis from 2025-05-21 23:01:25 (a year ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Lavasoft.AppCore
MD5: 1aa8da2640e7f6ea8f7c0cdfc5f4024e
Size: 118 KB
First Published: 2020-07-01 20:22:41 (5 years ago)
Latest Published: 2025-05-21 23:01:25 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-05-21 23:01:25 (a year ago)
Signed By: Lavasoft Limited
Status: Valid

The signature on Lavasoft.AppCore.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%\lavasoft\web companion

ThreatInfo has observed Lavasoft.AppCore.dll 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 62.1%
Windows 7 31.0%
Windows 8.1 3.4%
Windows XP 3.4%

The most common operating system signal for Lavasoft.AppCore.dll is Windows 10 with 62.1% 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.

Lavasoft.AppCore.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x0001c21e
Image base 0x10000000

.NET Info:

MVID: 62070a56-bd75-4235-98cb-d06c49a5ec5a
Typelib ID: 8ff2ee18-6017-46f0-9078-ec1c1b1ff0bf

PE Sections:

Sections 3
Raw data 109056

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

.text 107520 bytes · 98.6% of section data
MD5 e78a219d5bd59b38c91a7c434077b981
.rsrc 1024 bytes · 0.9% of section data
MD5 536c473d27e9cff08ae3887a13a69b13
.reloc 512 bytes · 0.5% of section data
MD5 99a24dd4b00db25a94a1ae41836c7d6d

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 1aa8da2640e7f6ea8f7c0cdfc5f4024e.
  • 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.