GridinSoft Threat Intelligence
nvcuvid32.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2021-10-26 20:57:12 (4 years ago); latest analysis 2021-10-26 20:57:12 (4 years ago).
Company metadata: NVIDIA Corporation. Product metadata: NVIDIA CUDA Video Decode API.
Signed by Nvidia Corporation;Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
nvcuvid32.dll is a Windows file recorded in the ThreatInfo database. It is associated with NVIDIA CUDA Video Decode API. The reported company name is NVIDIA Corporation. The current detection status is Undefined, based on the latest analysis from 2021-10-26 20:57:12 (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.
File Details
| Product Name: | NVIDIA CUDA Video Decode API |
| Company Name: | NVIDIA Corporation |
| MD5: | 7232bac51c0b4a1e4e1458a0b76e8f92 |
| Size: | 7 MB |
| First Published: | 2021-10-26 20:57:12 (4 years ago) |
| Latest Published: | 2021-10-26 20:57:12 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-10-26 20:57:12 (4 years ago) |
Overview
| Signed By: | Nvidia Corporation;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on nvcuvid32.dll 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.
Common Places:
| %localappdata%\innovative solutions\drivermax\agent\uploads\cx08762q0d243wf636cv8fet00p33qx0q86wjk1yro03x4qe8k\display |
ThreatInfo has observed nvcuvid32.dll 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.
Geographic signal
Observed country distribution
ThreatInfo has seen nvcuvid32.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Japan with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for nvcuvid32.dll 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.
Analysis
nvcuvid32.dll 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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
9b44bba3c2bb67d876c53651ae9e6900
faefd77e88d51bd27b8c746d02b5bb56
2526b82fd3090d5757a8d00ff011493a
9d8437563ec0275f4e5345c808412291
c573bd7cea296a9c5d230ca6b5aee1a6
097923a6dda745292fe593cd4d9140d9
b1daeab1b2da236208732f8fcc0ff113
d30afdd072df94668565666e072d89bb
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.