GridinSoft Threat Intelligence

pcid.dll file report

Under review File reputation report
MD5 c966c7a461c534843422771ce3a04a12
Latest seen 2021-02-13 04:32:15 (5 years ago)
First seen 2017-05-21 21:04:52 (9 years ago)
Size 127 KB
Signed by OSTOTO CO. LIMITED

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 21:04:52 (9 years ago); latest analysis 2021-02-13 04:32:15 (5 years ago).

Publisher context

Product metadata: pcid 动态链接库.

Digital signature

Signed by OSTOTO CO. LIMITED. 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.

pcid.dll is a Windows file recorded in the ThreatInfo database. It is associated with pcid 动态链接库. The current detection status is Undefined, based on the latest analysis from 2021-02-13 04:32:15 (5 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: pcid 动态链接库
MD5: c966c7a461c534843422771ce3a04a12
Size: 127 KB
First Published: 2017-05-21 21:04:52 (9 years ago)
Latest Published: 2021-02-13 04:32:15 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-02-13 04:32:15 (5 years ago)
Signed By: OSTOTO CO. LIMITED
Status: Valid

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

%localappdata%\hwifisvc
%localappdata%
%programfiles%\ostotosoft
%programfiles%

ThreatInfo has observed pcid.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 55.4%
Windows 7 36.9%
Windows 8.1 6.2%
Windows Vista 1.5%

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

pcid.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 0x000059cd
Image base 0x10000000

PE Sections:

Sections 5
Raw data 110592

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

.text 73728 bytes · 66.7% of section data
MD5 1b3a5a3c40b022cb9d8d08bfe77d3fca
.rdata 16384 bytes · 14.8% of section data
MD5 ce48a09047a5403a6875ecba60dbc5fc
.data 8192 bytes · 7.4% of section data
MD5 3d21e249ad12d3de04683b06540979b2
.rsrc 4096 bytes · 3.7% of section data
MD5 d339bd68724b8a9524ba800ec6fbb498
.reloc 8192 bytes · 7.4% of section data
MD5 c991fce84f5f422d53df3406806f73c5

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 c966c7a461c534843422771ce3a04a12.
  • 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.