GridinSoft Threat Intelligence

IntcDAud.sys file report

Under review File reputation report
MD5 75f82406df455d812101146ee4eb6fcd
Latest seen 2021-09-29 20:43:18 (4 years ago)
First seen 2017-07-26 03:25:23 (8 years ago)
Size 470 KB
Signed by Intel(R) OWR

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-07-26 03:25:23 (8 years ago); latest analysis 2021-09-29 20:43:18 (4 years ago).

Publisher context

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

Digital signature

Signed by Intel(R) OWR. 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-09-29 20:43:18 (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.

Product Name: Intel(R) Display Audio
Company Name: Intel(R) Corporation
MD5: 75f82406df455d812101146ee4eb6fcd
Size: 470 KB
First Published: 2017-07-26 03:25:23 (8 years ago)
Latest Published: 2021-09-29 20:43:18 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-09-29 20:43:18 (4 years ago)
Signed By: Intel(R) OWR
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.

%commonappdata%\reviversoft\driver reviver\downloads\118\16bc0a52-f7b2-47cb-93e4-a63ecc7f328f
%commonappdata%\reviversoft\driver reviver\unplugged drivers
%commonappdata%\reviversoft\driver reviver\downloads\93
%commonappdata%\reviversoft\pc reviver\s-1-5-21-1787136818-1417875359-2783829682-1000\driver updater\unplugged drivers
%commonappdata%\reviversoft\driver reviver\downloads\94
%commonappdata%\reviversoft\driver reviver\downloads\c4312697-a9b4-4bd6-8662-dcec35b37015
%localappdata%\slimware utilities inc\slimdrivers\backups\20170116t020338479990\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 8.1 57.1%
Windows 8 14.3%
Windows 7 14.3%
Windows 10 14.3%

The most common operating system signal for IntcDAud.sys is Windows 8.1 with 57.1% 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 11
Raw data 460800

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

.text 22528 bytes · 4.9% of section data
MD5 7c6a9a222e7aaa967cb0864c4350987f
CODE 6144 bytes · 1.3% of section data
MD5 530241105c2526f9075516089747487a
.rdata 26112 bytes · 5.7% of section data
MD5 10062ae9ee001570bcc1de370db912b8
.data 512 bytes · 0.1% of section data
MD5 5ca140c64ff0800660ee6dd6d378c7bc
.pdata 14336 bytes · 3.1% of section data
MD5 ce744628ccd7c6fe1393714af0538b96
text 3072 bytes · 0.7% of section data
MD5 981ee8f34cc45fb4cfcfd2c38f9a890c
data 10240 bytes · 2.2% of section data
MD5 a6643ae545092962a14d7bee1a5b20fe
PAGE 371712 bytes · 80.7% of section data
Uncommon name
MD5 7a428e69768c33648547611975b37ea8
INIT 2048 bytes · 0.4% of section data
Uncommon name
MD5 2d48c0107df37b8bb6e2c9f8ea75cfaf
.rsrc 1024 bytes · 0.2% of section data
MD5 ba60ec8b0c3bc59c69d8d4358962a1ea
.reloc 3072 bytes · 0.7% of section data
MD5 84a670ffa9725356e0cb5bfcd33bef2c

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 75f82406df455d812101146ee4eb6fcd.
  • 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.