SAntivirusShell86_v102228.dll file report

MD5 4df86026854a8489cded076f63bfb205
Latest seen 2024-04-11 23:06:30 (2 years ago)
First seen 2021-05-06 20:57:37 (5 years ago)
Size 154 KB
Publisher Сorp DCom
Product Сorp DCom

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-05-06 20:57:37 (5 years ago); latest analysis 2024-04-11 23:06:30 (2 years ago).

Publisher context

Company metadata: Сorp DCom . Product metadata: Сorp DCom .

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.

SAntivirusShell86_v102228.dll is a Windows file recorded in the ThreatInfo database. It is associated with Сorp DCom . The reported company name is Сorp DCom . The current detection status is Undefined, based on the latest analysis from 2024-04-11 23:06:30 (2 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: Сorp DCom
Company Name: Сorp DCom
MD5: 4df86026854a8489cded076f63bfb205
Size: 154 KB
First Published: 2021-05-06 20:57:37 (5 years ago)
Latest Published: 2024-04-11 23:06:30 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-04-11 23:06:30 (2 years ago)
Signed By: Digital Communications Inc
Status: Valid

The signature on SAntivirusShell86_v102228.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.

%commonappdata%\santivirus
%commonappdata%\santivirus
%programfiles%\digital communications
%commonappdata%\santivirus
%programfiles%\digital communications
%programfiles%\digital communications
%programfiles%\digital communications
%programfiles%\digital communications
%commonappdata%\santivirus
%commonappdata%\santivirus

ThreatInfo has observed SAntivirusShell86_v102228.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.

13.3%
13.3%
13.3%
13.3%
6.7%
6.7%
6.7%
6.7%
6.7%
6.7%
6.7%

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

Windows 10 68.8%
Windows 7 18.8%
Windows 8.1 12.5%

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

SAntivirusShell86_v102228.dll is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x00003ccc

PE Sections:

Name Size of data MD5
.text 86528 1cbbe52506ef11ba124b82914ea1613e
.fgd 512 d4dfce44aef2e9fa3da8780c506c2c53
.fad 512 05c4a7fc2b010b2b19654f847abe6a76
.ifad 512 2639c56499ade5bfd21dd0a9318d8a11
.fid 512 294d67cbc70af67e2b401ce37ecef11b
.fir 512 57521782f984064be1e890557c4a5070
.fiy 512 2af09fcb5f5f002ae67bdc216f2547ff
.fey 512 c70cae55b74b87f005d1174cfcff73c7
.fgh 512 8345607bda42185bbaa9ed0e37f26053
.fgha 512 44e084719585897442aa6b9de28f73c6
.fygih 512 67862768191e4ea103860425c1a1ef73
.uifgh 512 3e8e0341b7b836376eeabc7e75dcadac
.fghdf 1024 5ba67f91bf9e165a54672190b3a0e521
.fghf 512 8b1111c9cd1166105230b093b770950a
.fider 512 3edf3c59d8e8a461fef633cb47de97cc
.fidet 512 803059e689da376e2d0d889200ae0cd3
.fhid 512 ef8d82eca2cb2764fd57e122f682f0b2
.fido 512 5cbee32eeccc563230e6dda7f56aa5e8
.rdata 32768 052e6b495cee9ee517b1220483db0511
.data 3072 cbbe38c9d3dd432ff8796c433c818dd9
.gfids 512 d29c1d5684733e199a2dc801254bff92
.tls 512 1f354d76203061bfdd5a53dae48d5435
.rsrc 3584 1bfa35b18e1a78f0dec8522b5a84abde
.reloc 5632 ae1a6c5336e22a7c73e7a5e5b610ba90

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.

More information: