GridinSoft Threat Intelligence

InstStub.exe file report

Clean record File reputation report
MD5 eccbff701cb37ac9abb045855543940e
Latest seen 2025-12-07 23:06:18 (5 months ago)
First seen 2025-12-07 23:06:18 (5 months ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2025-12-07 23:06:18 (5 months ago); latest analysis 2025-12-07 23:06:18 (5 months ago).

Publisher context

Company metadata: Symantec Corporation. Product metadata: Norton Security Scan.

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.

InstStub.exe is a Windows file recorded in the ThreatInfo database. It is associated with Norton Security Scan. The reported company name is Symantec Corporation. The current detection status is Clean, based on the latest analysis from 2025-12-07 23:06:18 (5 months 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 Security Scan
Company Name: Symantec Corporation
MD5: eccbff701cb37ac9abb045855543940e
Size: 1 MB
First Published: 2025-12-07 23:06:18 (5 months ago)
Latest Published: 2025-12-07 23:06:18 (5 months ago)
Status: Clean (on last analysis)
Analysis Date: 2025-12-07 23:06:18 (5 months 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%\nortoninstaller\{397e31aa-0d78-4649-a01c-339d73a2ed35}\nss\licensetype

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

InstStub.exe 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 0x0005377a
Image base 0x00400000

PE Sections:

Sections 5
Raw data 1090048

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

.text 574464 bytes · 52.7% of section data
MD5 68d83cbe9987219771873eb340a92378
.rdata 183808 bytes · 16.9% of section data
MD5 78dfa6e9ffe3c931fb58b96eed942003
.data 6656 bytes · 0.6% of section data
MD5 2cd99c2d92006776c8ca75c2175c524f
.rsrc 280576 bytes · 25.7% of section data
MD5 e4900888a9cdacd5366b7020b451c439
.reloc 44544 bytes · 4.1% of section data
MD5 391d49af05a441e3f0bfdbae6dca2f58

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 eccbff701cb37ac9abb045855543940e.
  • 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.