GridinSoft Threat Intelligence

drcom.dll file report

Clean record File reputation report
MD5 5fe62f26aa1c87d740a7e783faa9b4b4
Latest seen 2021-12-12 21:32:13 (4 years ago)
First seen 2021-12-12 21:32:13 (4 years ago)
Size 1008 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-12-12 21:32:13 (4 years ago); latest analysis 2021-12-12 21:32:13 (4 years ago).

Digital signature

Signed by Beijing Kingsoft Security software Co.,Ltd. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

drcom.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-12-12 21:32:13 (4 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

MD5: 5fe62f26aa1c87d740a7e783faa9b4b4
Size: 1008 KB
First Published: 2021-12-12 21:32:13 (4 years ago)
Latest Published: 2021-12-12 21:32:13 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-12-12 21:32:13 (4 years ago)
Signed By: Beijing Kingsoft Security software Co.,Ltd
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%\kingsoft\kingsoft antivirus\vipapp

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

Windows 10 100.0%

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

drcom.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 0x00237000
Image base 0x10000000

PE Sections:

Sections 6
Raw data 1019904

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

188416 bytes · 18.5% of section data
Uncommon name
MD5 075d42ebd04212389b2c42d5dc9479cb
.rsrc 4096 bytes · 0.4% of section data
MD5 1aed2289ed5d06039ebe5704671d32f8
.idata 4096 bytes · 0.4% of section data
Uncommon name
MD5 feed6f32891c85bee0429504c6ad2125
4096 bytes · 0.4% of section data
Uncommon name
MD5 52814db1b56e3e5a0b96c1d22463c135
bfjguxfm 815104 bytes · 79.9% of section data
Uncommon name
MD5 1e10b9f08621f5b06bd2347b9901c938
cvhdoqyd 4096 bytes · 0.4% of section data
Uncommon name
MD5 419f2be9fda741fffee2bb07a6402e63

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 5fe62f26aa1c87d740a7e783faa9b4b4.
  • 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.