GridinSoft Threat Intelligence

WLOfficeUtils.dll file report

Under review File reputation report
MD5 8efe0ed12c7c37bfa2f64a079b39f2f5
Latest seen 2025-01-04 23:01:17 (a year ago)
First seen 2020-01-30 09:17:15 (6 years ago)
Size 471 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-01-30 09:17:15 (6 years ago); latest analysis 2025-01-04 23:01:17 (a year ago).

Publisher context

Product metadata: WLOfficeUtils ActiveX DLL.

Digital signature

Signed by Sorentio Systems Ltd. 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.

WLOfficeUtils.dll is a Windows file recorded in the ThreatInfo database. It is associated with WLOfficeUtils ActiveX DLL. The current detection status is Undefined, based on the latest analysis from 2025-01-04 23:01:17 (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: WLOfficeUtils ActiveX DLL
MD5: 8efe0ed12c7c37bfa2f64a079b39f2f5
Size: 471 KB
First Published: 2020-01-30 09:17:15 (6 years ago)
Latest Published: 2025-01-04 23:01:17 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-01-04 23:01:17 (a year ago)
Signed By: Sorentio Systems Ltd
Status: Valid

The signature on WLOfficeUtils.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.

%commondir%

ThreatInfo has observed WLOfficeUtils.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 60.0%
Windows 7 40.0%

The most common operating system signal for WLOfficeUtils.dll is Windows 10 with 60.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.

WLOfficeUtils.dll 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 0x00059ce2
Image base 0x10000000

PE Sections:

Sections 5
Raw data 458752

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

.text 368640 bytes · 80.4% of section data
MD5 06d7a7be460aa470d02e72c368fb5dce
.rdata 57344 bytes · 12.5% of section data
MD5 b2f84fb723cda5eb49f821e36b78dfbd
.data 8192 bytes · 1.8% of section data
MD5 ad0fd29e5438c9a60a0a5fe6ee6bc794
.rsrc 8192 bytes · 1.8% of section data
MD5 7b0d17a059fa49ec87339d9d44179126
.reloc 16384 bytes · 3.6% of section data
MD5 44b94e5672b6a3e14bead65559fb8852

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 8efe0ed12c7c37bfa2f64a079b39f2f5.
  • 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.