GridinSoft Threat Intelligence

IntcDAud.sys file report

Under review File reputation report
MD5 9a8079fed84ba98e471102fa21dc339d
Latest seen 2024-01-30 23:59:07 (2 years ago)
First seen 2018-03-29 19:06:53 (8 years ago)
Size 800 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-03-29 19:06:53 (8 years ago); latest analysis 2024-01-30 23:59:07 (2 years ago).

Publisher context

Company metadata: Intel(R) Corporation. Product metadata: Intel(R) Display Audio.

Digital signature

Signed by Intel(R) Display Audio. 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.

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.

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)
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.

%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.

Windows 10 100.0%

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.

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.

Format pe
Architecture 64-bit
Subsystem Native
Entry point 0x000c3000
Image base 0x0000000000010000

PE Sections:

Sections 10
Raw data 799232

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

.text 39424 bytes · 4.9% of section data
MD5 5bbf2ff80816210baef46957928ecb00
CODE 24064 bytes · 3.0% of section data
MD5 570c7032f89b90bce3cb6331a8954f22
.rdata 46592 bytes · 5.8% of section data
MD5 02c253bb982980bb28126eae7a2553b8
.data 11264 bytes · 1.4% of section data
MD5 d3fe67ed9b96cf7e6fbd6311491d1af3
.pdata 23040 bytes · 2.9% of section data
MD5 eba6fc9c56639ca92ed775dcab3c01fc
.gfids 512 bytes · 0.1% of section data
Uncommon name
MD5 5e94b262725836db5cb5894ee12ecc33
PAGE 638976 bytes · 79.9% of section data
Uncommon name
MD5 4ff4abcbd5f92b0be0bc87a82ae0037b
INIT 3072 bytes · 0.4% of section data
Uncommon name
MD5 df71037aa19960c9f786ca186771ce2c
.rsrc 6144 bytes · 0.8% of section data
MD5 9d9735aa8fce3db4fed2878341ac29b2
.reloc 6144 bytes · 0.8% of section data
MD5 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.

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 9a8079fed84ba98e471102fa21dc339d.
  • 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.