GridinSoft Threat Intelligence

CLTVault.dll file report

Clean record File reputation report
MD5 60d47be6aad113a4b39f064ff945b55c
Latest seen 2023-02-17 23:47:25 (3 years ago)
First seen 2023-02-17 23:47:25 (3 years ago)
Size 625 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-02-17 23:47:25 (3 years ago); latest analysis 2023-02-17 23:47:25 (3 years ago).

Publisher context

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

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.

CLTVault.dll is a Windows file recorded in the ThreatInfo database. It is associated with Norton AntiVirus. The reported company name is Symantec Corporation. The current detection status is Clean, based on the latest analysis from 2023-02-17 23:47:25 (3 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 AntiVirus
Company Name: Symantec Corporation
MD5: 60d47be6aad113a4b39f064ff945b55c
Size: 625 KB
First Published: 2023-02-17 23:47:25 (3 years ago)
Latest Published: 2023-02-17 23:47:25 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-02-17 23:47:25 (3 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.

%sysdrive%\windows.old\users\lauris_inc\appdata\local\temp\nav14.2\nav\parent

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

CLTVault.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 0x00040000
Image base 0x10000000

PE Sections:

Sections 5
Raw data 624160

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

.text 120928 bytes · 19.4% of section data
MD5 857c0e254e3858c18ffc61db17940e15
.rdata 117776 bytes · 18.9% of section data
MD5 6c8c404a793f27c062e7f0907985687f
.data 4528 bytes · 0.7% of section data
MD5 677fb1af777c552d9412d8a84dd07b3d
.rsrc 4096 bytes · 0.7% of section data
MD5 dc11adef3c450fb8d5ffc2a6b8f661d4
.asdfas 376832 bytes · 60.4% of section data
Uncommon name
MD5 55aea5906a4f420e6e3663c3e00ace0d

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 60d47be6aad113a4b39f064ff945b55c.
  • 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.