GridinSoft Threat Intelligence
SegurazoKD.sys file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2019-07-20 03:25:05 (6 years ago); latest analysis 2022-03-20 23:45:27 (4 years ago).
Company metadata: Digital Communications Inc. Product metadata: Segurazo Antivirus.
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
SegurazoKD.sys is a Windows file recorded in the ThreatInfo database. It is associated with Segurazo Antivirus. The reported company name is Digital Communications Inc. The current detection status is Undefined, based on the latest analysis from 2022-03-20 23:45:27 (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: | Segurazo Antivirus |
| Company Name: | Digital Communications Inc |
| MD5: | 3baf005c4c0dc4d94e2462a0dc2ce827 |
| Size: | 82 KB |
| First Published: | 2019-07-20 03:25:05 (6 years ago) |
| Latest Published: | 2022-03-20 23:45:27 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2022-03-20 23:45:27 (4 years ago) |
Overview
| Signed By: | Digital Communications Inc.;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on SegurazoKD.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% |
| %sysdrive%\windows.old\program files (x86) |
| %windir% |
ThreatInfo has observed SegurazoKD.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 SegurazoKD.sys across 23 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Taiwan with 21.7% 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 SegurazoKD.sys is Windows 10 with 84.9% 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
SegurazoKD.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
ccd1fe044d2e234bcde92d4777b0a3aa
a1da731a9ca15d0c2e4fd732a714315c
e495e10881403f458ec87fefff29065f
e4e4ef23d6e831181bbefcacfb3754c9
1cf2856b26691be80e10679aee1138e4
b6cc598d293e98e884850830bb74a6a5
3ee3be28d61e61715662b99da2fce986
dfa88881a9c0b68ac4294f315a068c50
74e42e926b58b2846b4b2079f9e24731
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.