GridinSoft Threat Intelligence

WTLIC.dll file report

Clean record File reputation report
MD5 1213aeeaf3daa224c64f8421722f2d26
Latest seen 2023-07-02 23:04:53 (2 years ago)
First seen 2023-07-02 23:04:53 (2 years ago)
Size 97 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-07-02 23:04:53 (2 years ago); latest analysis 2023-07-02 23:04:53 (2 years ago).

Publisher context

Company metadata: Symantec Corporation. Product metadata: Norton SystemWorks.

Digital signature

Signed by Symantec 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.

WTLIC.dll is a Windows file recorded in the ThreatInfo database. It is associated with Norton SystemWorks. The reported company name is Symantec Corporation. The current detection status is Clean, based on the latest analysis from 2023-07-02 23:04:53 (2 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: Norton SystemWorks
Company Name: Symantec Corporation
MD5: 1213aeeaf3daa224c64f8421722f2d26
Size: 97 KB
First Published: 2023-07-02 23:04:53 (2 years ago)
Latest Published: 2023-07-02 23:04:53 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-07-02 23:04:53 (2 years ago)
Signed By: Symantec 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.

%programfiles%\symantec

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

WTLIC.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 0x00012000
Image base 0x10000000

PE Sections:

Sections 5
Raw data 82032

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

.text 40784 bytes · 49.7% of section data
MD5 55d719e9ff14fe251ec7d4b28558924f
.rdata 17824 bytes · 21.7% of section data
MD5 15b3a077e6e22215be2fa43794a5e70f
.data 1312 bytes · 1.6% of section data
MD5 12765773304e9231e1e900b906f7aa77
.rsrc 1632 bytes · 2.0% of section data
MD5 4bb418894b825bd6190a23057667ff31
.asdfas 20480 bytes · 25.0% of section data
Uncommon name
MD5 eabfb814a2d9a61f8fce6dbafbfc8e28

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 1213aeeaf3daa224c64f8421722f2d26.
  • 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.