GridinSoft Threat Intelligence

IntcDAud.sys file report

Under review File reputation report
MD5 eae20db9dc1366b9a1c558c58229ad65
Latest seen 2021-03-27 21:53:47 (5 years ago)
First seen 2019-06-15 11:09:16 (6 years ago)
Size 468 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-06-15 11:09:16 (6 years ago); latest analysis 2021-03-27 21:53:47 (5 years ago).

Publisher context

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

Digital signature

Signed by Intel 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.

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 2021-03-27 21:53:47 (5 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: eae20db9dc1366b9a1c558c58229ad65
Size: 468 KB
First Published: 2019-06-15 11:09:16 (6 years ago)
Latest Published: 2021-03-27 21:53:47 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-27 21:53:47 (5 years ago)

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.

%localappdata%\slimware utilities inc\slimdrivers\backups\20190528t212349909106\hdaudio
%localappdata%\slimware utilities inc\slimdrivers\backups\20190615t040518305800\hdaudio
%commonappdata%\reviversoft\driver reviver\downloads\87307a56-22a1-4cbf-9a72-0a441ce89f9b
%commonappdata%\reviversoft\driver reviver\downloads\110
%commonappdata%\winzip\winzip driver updater\unplugged drivers
%appdata%\driverfinder\backup
%commonappdata%\winzip\winzip driver updater\downloads\109
%commonappdata%\winzip\winzip driver updater\downloads\a184bb58-d0c4-4598-9dc7-4b986f88d914
%commonappdata%\reviversoft\driver reviver\downloads\a7711acc-cace-48e6-afb4-561ddf902677
%commonappdata%\reviversoft\driver reviver\downloads\49

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 75.0%
Windows 7 19.4%
Windows 8.1 5.6%

The most common operating system signal for IntcDAud.sys is Windows 10 with 75.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 0x00074000
Image base 0x0000000000010000

PE Sections:

Sections 10
Raw data 462336

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

.text 25600 bytes · 5.5% of section data
MD5 101650d602e0b9efb6ac7ee5d2febcb3
CODE 6144 bytes · 1.3% of section data
MD5 b3b17d8029ac730bcd29b1f4d2b67d7b
.rdata 26624 bytes · 5.8% of section data
MD5 7ef458ea609e7a3131b75c0f3a3ce2ed
.data 10752 bytes · 2.3% of section data
MD5 b637ef685f514515a979405c9a746d88
.pdata 14336 bytes · 3.1% of section data
MD5 a8300dd06788c695538a16fc9b2d29c0
.gfids 512 bytes · 0.1% of section data
Uncommon name
MD5 5e94b262725836db5cb5894ee12ecc33
PAGE 372224 bytes · 80.5% of section data
Uncommon name
MD5 8334d40f18c10b6b2d3e9fc4a4f1b5e1
INIT 2048 bytes · 0.4% of section data
Uncommon name
MD5 221900afcb8b860592ac4aefb28ebecb
.rsrc 1024 bytes · 0.2% of section data
MD5 403cc6c2afba0957560b4732c3e1e533
.reloc 3072 bytes · 0.7% of section data
MD5 71ed185eda0819beff8c998c45ccdcc4

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