GridinSoft Threat Intelligence

NSWSTE.dll file report

Clean record File reputation report
MD5 251ecdea778d743eea0c4ea3854190fc
Latest seen 2023-07-02 23:08:02 (2 years ago)
First seen 2023-07-02 23:05:17 (2 years ago)
Size 189 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-07-02 23:05:17 (2 years ago); latest analysis 2023-07-02 23:08:02 (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.

NSWSTE.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:08:02 (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: 251ecdea778d743eea0c4ea3854190fc
Size: 189 KB
First Published: 2023-07-02 23:05:17 (2 years ago)
Latest Published: 2023-07-02 23:08:02 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-07-02 23:08:02 (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.

%sysdrive%\netscape
%sysdrive%\system volume information\_restore{95152275-a646-4568-b4ad-fec19f92a712}

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

NSWSTE.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 0x00022000
Image base 0x10000000

PE Sections:

Sections 5
Raw data 173888

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

.text 85424 bytes · 49.1% of section data
MD5 06913e06f12f80d7b5fb713de9005913
.rdata 36960 bytes · 21.3% of section data
MD5 9d831caf1b03db67c1fb417c075572ec
.data 1392 bytes · 0.8% of section data
MD5 c7146ba9845a207637cc8133e5bddc69
.rsrc 960 bytes · 0.6% of section data
MD5 a3af1429b0a9a1b4318fe95da3b9f98a
.asdfas 49152 bytes · 28.3% of section data
Uncommon name
MD5 415bf6f4f15bd668c1e610e6363b94a0

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 251ecdea778d743eea0c4ea3854190fc.
  • 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.