GridinSoft Threat Intelligence

NVIDIA Package Launcher file report

Clean record File reputation report
MD5 5114bf28a575264366c1ad0f5fe76fd0
Latest seen 2025-11-10 23:02:05 (6 months ago)
First seen 2023-04-16 23:54:27 (3 years ago)
Size 28 MB
Publisher NVIDIA Corporation
Signed by NVIDIA Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-04-16 23:54:27 (3 years ago); latest analysis 2025-11-10 23:02:05 (6 months ago).

Publisher context

Company metadata: NVIDIA Corporation. Product metadata: NVIDIA Package Launcher.

Digital signature

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

NVIDIA Package Launcher is a Windows file recorded in the ThreatInfo database. It is associated with NVIDIA Package Launcher. The reported company name is NVIDIA Corporation. The current detection status is Clean, based on the latest analysis from 2025-11-10 23:02:05 (6 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: NVIDIA Package Launcher
Company Name: NVIDIA Corporation
MD5: 5114bf28a575264366c1ad0f5fe76fd0
Size: 28 MB
First Published: 2023-04-16 23:54:27 (3 years ago)
Latest Published: 2025-11-10 23:02:05 (6 months ago)
Status: Clean (on last analysis)
Analysis Date: 2025-11-10 23:02:05 (6 months ago)
Signed By: NVIDIA 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.

%localappdata%\innovative solutions\drivermax\agent

ThreatInfo has observed NVIDIA Package Launcher 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 90.9%
Windows 7 9.1%

The most common operating system signal for NVIDIA Package Launcher is Windows 10 with 90.9% 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.

NVIDIA Package Launcher 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 0x00051401
Image base 0x00400000

PE Sections:

Sections 4
Raw data 752640

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

.text 462848 bytes · 61.5% of section data
MD5 f5aab9fcd36b137b360f142f070c1110
.rdata 107008 bytes · 14.2% of section data
MD5 7609f7ceae35f5098ae142d1e9b854f5
.data 32256 bytes · 4.3% of section data
MD5 e368aa3ca99ece50008c551f3a64c97b
.rsrc 150528 bytes · 20.0% of section data
MD5 6ea47b7db072ad02b09989a48abf6a59

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 5114bf28a575264366c1ad0f5fe76fd0.
  • 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.