GridinSoft Threat Intelligence
IntcDAud.sys file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2018-03-29 19:06:53 (8 years ago); latest analysis 2024-01-30 23:59:07 (2 years ago).
Company metadata: Intel(R) Corporation. Product metadata: Intel(R) Display Audio.
Signed by Intel(R) Display Audio. 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
IntcDAud.sys is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Display Audio. The reported company name is Intel(R) Corporation. The current detection status is Undefined, based on the latest analysis from 2024-01-30 23:59:07 (2 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: | Intel(R) Display Audio |
| Company Name: | Intel(R) Corporation |
| MD5: | 9a8079fed84ba98e471102fa21dc339d |
| Size: | 800 KB |
| First Published: | 2018-03-29 19:06:53 (8 years ago) |
| Latest Published: | 2024-01-30 23:59:07 (2 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2024-01-30 23:59:07 (2 years ago) |
Overview
| Signed By: | Intel(R) Display Audio |
| Status: | Valid |
The signature on IntcDAud.sys 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:
| %appdata%\driverfinder\backup |
| %appdata%\uniblue\driverscanner\drivers\154853\gfx_win10_64_15.65.4.4944\displayaudio |
| %appdata%\uniblue\driverscanner\drivers\154866\gfx_win10_64_15.65.4.4944_ky\displayaudio |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20180408t165729635970\hdaudio |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20180703t202251920486\hdaudio |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20180705t124647080615\hdaudio |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20190513t030651232912\hdaudio |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20190205t003333041424\hdaudio |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20190205t012745260899\hdaudio |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20190215t185427088839\hdaudio |
ThreatInfo has observed IntcDAud.sys 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 IntcDAud.sys across 6 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Colombia with 28.6% 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 IntcDAud.sys 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
IntcDAud.sys is identified as pe for 64-bit systems. The subsystem is Native. 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.
5bbf2ff80816210baef46957928ecb00
570c7032f89b90bce3cb6331a8954f22
02c253bb982980bb28126eae7a2553b8
d3fe67ed9b96cf7e6fbd6311491d1af3
eba6fc9c56639ca92ed775dcab3c01fc
5e94b262725836db5cb5894ee12ecc33
4ff4abcbd5f92b0be0bc87a82ae0037b
df71037aa19960c9f786ca186771ce2c
9d9735aa8fce3db4fed2878341ac29b2
672ad1af70fe89f8640d9e071ab58892
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.