GridinSoft Threat Intelligence

SAntivirusShell86_v102149.dll file report

Under review File reputation report
MD5 4add70144cbcbb03ea9c7015f11bf2b3
Latest seen 2021-08-08 20:21:21 (4 years ago)
First seen 2020-03-19 00:08:54 (6 years ago)
Size 156 KB
Publisher Digital Com. Inc
Product Digital Com. Inc
Signed by Digital Communications Inc

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-03-19 00:08:54 (6 years ago); latest analysis 2021-08-08 20:21:21 (4 years ago).

Publisher context

Company metadata: Digital Com. Inc. Product metadata: Digital Com. Inc.

Digital signature

Signed by Digital Communications Inc. 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.

File context

SAntivirusShell86_v102149.dll is a Windows file recorded in the ThreatInfo database. It is associated with Digital Com. Inc. The reported company name is Digital Com. Inc. The current detection status is Undefined, based on the latest analysis from 2021-08-08 20:21:21 (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: Digital Com. Inc
Company Name: Digital Com. Inc
MD5: 4add70144cbcbb03ea9c7015f11bf2b3
Size: 156 KB
First Published: 2020-03-19 00:08:54 (6 years ago)
Latest Published: 2021-08-08 20:21:21 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-08-08 20:21:21 (4 years ago)

Overview

Signed By: Digital Communications Inc
Status: Valid

The signature on SAntivirusShell86_v102149.dll 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
%programfiles%\digital communications.del
%sysdrive%\windows.old\program files (x86)\digital communications

ThreatInfo has observed SAntivirusShell86_v102149.dll 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 SAntivirusShell86_v102149.dll across 10 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Thailand
Share 20.0%
Low High activity

The strongest geographic signal for this file is Thailand with 20.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 95.5%
Windows 7 4.5%

The most common operating system signal for SAntivirusShell86_v102149.dll is Windows 10 with 95.5% 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

SAntivirusShell86_v102149.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00004542
Image base 0x10000000

PE Sections:

Sections 16
Raw data 139264

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

.text 88576 bytes · 63.6% of section data
MD5 eae07c2c519b629409748b5b48150e63
.figd 512 bytes · 0.4% of section data
Uncommon name
MD5 523cdf8fb1845a1d9879ac0b55eab9db
.fiad 512 bytes · 0.4% of section data
Uncommon name
MD5 f8edcbc5445fa7b10c3c960c03b2d162
.fida 512 bytes · 0.4% of section data
Uncommon name
MD5 bdc5f4ea633a3704c2d54d7c0c24d09f
.fird 512 bytes · 0.4% of section data
Uncommon name
MD5 127c16532f6facc35eec29b45cc48531
.fidy 512 bytes · 0.4% of section data
Uncommon name
MD5 dabb82533275424390dcfd5a73afdd28
.fider 512 bytes · 0.4% of section data
Uncommon name
MD5 735554a6048e7b05d5c1a740beb7821e
.fidet 512 bytes · 0.4% of section data
Uncommon name
MD5 1219e3696e3d06329fa4adfbc4ebfc37
.fhid 512 bytes · 0.4% of section data
Uncommon name
MD5 911e58be9369d8d4ac80d9eaf99c1c0d
.fido 512 bytes · 0.4% of section data
Uncommon name
MD5 a77b2ebd10d7fc3fde463a41e7b0472d
.rdata 32768 bytes · 23.5% of section data
MD5 198c84181091f4dc0c6af92d82249295
.data 3072 bytes · 2.2% of section data
MD5 55e893c681197998710c00864eef19e9
.gfids 512 bytes · 0.4% of section data
Uncommon name
MD5 bdd1d79fcf2403d2c917d9f68aecc14c
.tls 512 bytes · 0.4% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 3584 bytes · 2.6% of section data
MD5 fff50587d4bb51757d56eb01969e1fac
.reloc 5632 bytes · 4.0% of section data
MD5 8f89324df4e16c44a1fc1727c03f9288

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 4add70144cbcbb03ea9c7015f11bf2b3.
  • 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.