GridinSoft Threat Intelligence
tasantiviruskd.sys file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2022-03-01 23:59:05 (4 years ago); latest analysis 2022-03-01 23:59:28 (4 years ago).
Company metadata: DlGlTAL COMMUNICATIONS INC. Product metadata: DlGlTAL COMMUNICATIONS INC.
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
tasantiviruskd.sys is a Windows file recorded in the ThreatInfo database. It is associated with DlGlTAL COMMUNICATIONS INC. The reported company name is DlGlTAL COMMUNICATIONS INC. The current detection status is Undefined, based on the latest analysis from 2022-03-01 23:59:28 (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.
File Details
| Product Name: | DlGlTAL COMMUNICATIONS INC |
| Company Name: | DlGlTAL COMMUNICATIONS INC |
| MD5: | a2796e6c1eba710c00efb4d4437ce501 |
| Size: | 96 KB |
| First Published: | 2022-03-01 23:59:05 (4 years ago) |
| Latest Published: | 2022-03-01 23:59:28 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2022-03-01 23:59:28 (4 years ago) |
Overview
| Signed By: | Digital Communications Inc;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on tasantiviruskd.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%\digital communications |
| %commonappdata%\santivirus |
ThreatInfo has observed tasantiviruskd.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 tasantiviruskd.sys across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Italy with 100.0% 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 tasantiviruskd.sys is Windows 7 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
tasantiviruskd.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.
cf4a347b1f1d4de8007c3984034238ce
b71e98df5709180b586f0b92cdfee758
80bc8e742e46e39fcf11237e7fe2f035
b3dbe1b70ba6aeca541e8a3fe0a3b630
756c159814ad16216484944ef2d60734
431d5b0b80b4689c36bbfd30d12f58f3
985082a1488076a090599ea1e8220c02
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.