GridinSoft Threat Intelligence

MSI Notification.exe file report

Clean record File reputation report
MD5 d4afc59ccb385a98544e3bbc5c7c22aa
Latest seen 2023-03-18 23:26:40 (3 years ago)
First seen 2023-03-18 23:26:40 (3 years ago)
Size 140 KB
Product Notifiaction

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-03-18 23:26:40 (3 years ago); latest analysis 2023-03-18 23:26:40 (3 years ago).

Publisher context

Company metadata: Micro-Star International Co., Ltd.. Product metadata: Notifiaction.

Digital signature

Signed by Micro-Star International CO., LTD.. 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.

MSI Notification.exe is a Windows file recorded in the ThreatInfo database. It is associated with Notifiaction. The reported company name is Micro-Star International Co., Ltd.. The current detection status is Clean, based on the latest analysis from 2023-03-18 23:26:40 (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: Notifiaction
Company Name: Micro-Star International Co., Ltd.
MD5: d4afc59ccb385a98544e3bbc5c7c22aa
Size: 140 KB
First Published: 2023-03-18 23:26:40 (3 years ago)
Latest Published: 2023-03-18 23:26:40 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-03-18 23:26:40 (3 years ago)
Signed By: Micro-Star International CO., LTD.
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%\msi\drive_e\temp\msi live update

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

MSI Notification.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 0x000239be
Image base 0x00400000

.NET Info:

MVID: 36d216e5-8cb6-4fce-a159-20ac88d34906
Typelib ID: 145d5143-058a-4718-b0cb-7c2d7389d95d

PE Sections:

Sections 3
Raw data 140288

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

.text 137728 bytes · 98.2% of section data
MD5 6a378637b1fe92ba5334e145baee6ad8
.rsrc 2048 bytes · 1.5% of section data
MD5 ba478e4ee0242d158aa00f3e8f4aedfd
.reloc 512 bytes · 0.4% of section data
MD5 003f559f408ab147827141597813567b

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