GridinSoft Threat Intelligence

WLTSCore4.dll file report

Under review File reputation report
MD5 4b82d4ff18cfcc1a8e9e9b7b27acf07c
Latest seen 2025-01-04 23:01:19 (a year ago)
First seen 2020-05-30 18:52:16 (5 years ago)
Size 503 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-05-30 18:52:16 (5 years ago); latest analysis 2025-01-04 23:01:19 (a year ago).

Publisher context

Product metadata: WLTSCore4 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.

WLTSCore4.dll is a Windows file recorded in the ThreatInfo database. It is associated with WLTSCore4 ActiveX DLL. The current detection status is Undefined, based on the latest analysis from 2025-01-04 23:01:19 (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: WLTSCore4 ActiveX DLL
MD5: 4b82d4ff18cfcc1a8e9e9b7b27acf07c
Size: 503 KB
First Published: 2020-05-30 18:52:16 (5 years ago)
Latest Published: 2025-01-04 23:01:19 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-01-04 23:01:19 (a year ago)
Signed By: Sorentio Systems Ltd
Status: Valid

The signature on WLTSCore4.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 WLTSCore4.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 100.0%

The most common operating system signal for WLTSCore4.dll 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.

WLTSCore4.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 0x000396e5
Image base 0x10000000

PE Sections:

Sections 5
Raw data 491520

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

.text 299008 bytes · 60.8% of section data
MD5 c1a3429b376cfa7b7b69c7912198328c
.rdata 102400 bytes · 20.8% of section data
MD5 4d9c2f182fc6ccfc52dd8e732b54ac29
.data 20480 bytes · 4.2% of section data
MD5 837fd03467d499158f712d21b7af95e9
.rsrc 32768 bytes · 6.7% of section data
MD5 15e16d027a9176b1c6b8a6cb88ddb523
.reloc 36864 bytes · 7.5% of section data
MD5 0911df0388b825886c6a66c91167b99a

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 4b82d4ff18cfcc1a8e9e9b7b27acf07c.
  • 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.