GridinSoft Threat Intelligence
SAntivirusKD.sys file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2020-01-16 08:08:41 (6 years ago); latest analysis 2023-02-20 23:23:57 (3 years ago).
Company metadata: Digital Comm. Inc. Product metadata: Antivirus Driver.
Signed by Digital Communications Inc.;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
SAntivirusKD.sys is a Windows file recorded in the ThreatInfo database. It is associated with Antivirus Driver. The reported company name is Digital Comm. Inc. The current detection status is Undefined, based on the latest analysis from 2023-02-20 23:23:57 (3 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: | Antivirus Driver |
| Company Name: | Digital Comm. Inc |
| MD5: | 82d03310b1ce3a5c9bc9a99084cbebb2 |
| Size: | 79 KB |
| First Published: | 2020-01-16 08:08:41 (6 years ago) |
| Latest Published: | 2023-02-20 23:23:57 (3 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2023-02-20 23:23:57 (3 years ago) |
Overview
| Signed By: | Digital Communications Inc.;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on SAntivirusKD.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:
| %programfiles% |
| %programfiles%\digital communications |
| %commonappdata%\santivirus |
ThreatInfo has observed SAntivirusKD.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 SAntivirusKD.sys across 16 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is India with 17.2% 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 SAntivirusKD.sys is Windows 7 with 67.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
SAntivirusKD.sys is identified as pe for 32-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.
33b49be2e584f94109794e4b584f5caf
56079b5bcd613256e6b177a5ab947930
be12bb2149434d1a398a0a1c0a23b109
ac8151ab9b344b7b4c7829a9f3e9f5a8
0f309ca9a7508a665a39df6cfc130b74
1688bfda1735aa105b5dc7e5dc31e536
c35fd80fed2395dd564830b3f6a527ec
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.