GridinSoft Threat Intelligence

CTM5xLNIKsdEKO1Dug4JZs3a.exe file report

Clean record File reputation report
MD5 10f4b4f75baa728bded1a06ca381744b
Latest seen 2023-10-24 23:38:27 (2 years ago)
First seen 2023-10-24 23:08:01 (2 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-10-24 23:08:01 (2 years ago); latest analysis 2023-10-24 23:38:27 (2 years ago).

Digital signature

Signed by Hewlett-Packard Company. 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.

CTM5xLNIKsdEKO1Dug4JZs3a.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2023-10-24 23:38:27 (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.

MD5: 10f4b4f75baa728bded1a06ca381744b
Size: 2 MB
First Published: 2023-10-24 23:08:01 (2 years ago)
Latest Published: 2023-10-24 23:38:27 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-10-24 23:38:27 (2 years ago)
Signed By: Hewlett-Packard Company
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.

%profile%\pictures

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

CTM5xLNIKsdEKO1Dug4JZs3a.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 0x005200e0
Image base 0x00400000

PE Sections:

Sections 7
Raw data 2240000

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

71168 bytes · 3.2% of section data
Uncommon name
MD5 ac540e83c3e6fb368d57c29416baf0de
76288 bytes · 3.4% of section data
Uncommon name
MD5 86b5f52e024aaf418ad006cc7d6d9c16
512 bytes · 0.0% of section data
Uncommon name
MD5 47aebfe0087d8984902e34d758aaaeab
.idata 512 bytes · 0.0% of section data
MD5 f423a5677f293093223692525921521c
.rsrc 91136 bytes · 4.1% of section data
MD5 38dadd0d41d940b76b3723abfa959597
.themida 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.boot 2000384 bytes · 89.3% of section data
Uncommon name
MD5 c63c8b39ec60d959f7bfc5244e0490b6

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 10f4b4f75baa728bded1a06ca381744b.
  • 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.