GridinSoft Threat Intelligence

YAMLFXC32.exe file report

Under review File reputation report
MD5 a76a655e0582633e9c19a41eeaf34d4b
Latest seen 2021-10-26 20:55:34 (4 years ago)
First seen 2021-10-26 20:55:34 (4 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-10-26 20:55:34 (4 years ago); latest analysis 2021-10-26 20:55:34 (4 years ago).

Digital signature

Signed by Nvidia Corporation;Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

YAMLFXC32.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-10-26 20:55:34 (4 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

MD5: a76a655e0582633e9c19a41eeaf34d4b
Size: 1 MB
First Published: 2021-10-26 20:55:34 (4 years ago)
Latest Published: 2021-10-26 20:55:34 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-10-26 20:55:34 (4 years ago)

The signature on YAMLFXC32.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%localappdata%\innovative solutions\drivermax\agent\uploads\cx08762q0d243wf636cv8fet00p33qx0q86wjk1yro03x4qe8k\display\pci_ven_10de&dev_11c6

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

YAMLFXC32.exe is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x000a2230
Image base 0x00400000

PE Sections:

Sections 5
Raw data 1748480

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

.text 912384 bytes · 52.2% of section data
MD5 fff054f74355ce551b8f69b70ec62d8c
.rdata 235008 bytes · 13.4% of section data
MD5 fef0f833d536e4cf00316e169d00c7f9
.data 557568 bytes · 31.9% of section data
MD5 6787e650a0da98f72186afefca0593d7
.rsrc 512 bytes · 0.0% of section data
MD5 91b4ac24d7756592fad3860a99fee481
.reloc 43008 bytes · 2.5% of section data
MD5 d482b05d9f05a92bb8d549dfdbc3797a

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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