GridinSoft Threat Intelligence

ConfigCenter.dll file report

Under review File reputation report
MD5 4695f9ad42320f33ccc917f674dff539
Latest seen 2024-09-08 23:01:05 (2 years ago)
First seen 2019-03-30 14:15:50 (7 years ago)
Size 448 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-03-30 14:15:50 (7 years ago); latest analysis 2024-09-08 23:01:05 (2 years ago).

Publisher context

Product metadata: ConfigCenterStub.

Digital signature

Signed by Beijing Qihu Technology Co., Ltd.. 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.

ConfigCenter.dll is a Windows file recorded in the ThreatInfo database. It is associated with ConfigCenterStub. The current detection status is Undefined, based on the latest analysis from 2024-09-08 23:01:05 (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: ConfigCenterStub
MD5: 4695f9ad42320f33ccc917f674dff539
Size: 448 KB
First Published: 2019-03-30 14:15:50 (7 years ago)
Latest Published: 2024-09-08 23:01:05 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-09-08 23:01:05 (2 years ago)
Signed By: Beijing Qihu Technology Co., Ltd.
Status: Valid

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

%programfiles%\ludashi
%programfiles%\ldslite

ThreatInfo has observed ConfigCenter.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 80.0%
Windows 7 20.0%

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

ConfigCenter.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 0x0002e735
Image base 0x10000000

PE Sections:

Sections 5
Raw data 442880

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

.text 332288 bytes · 75.0% of section data
MD5 3c6f649b7f41d694a5eea3f115bc948f
.rdata 73216 bytes · 16.5% of section data
MD5 8685cace2a440f010d976ff7bd5f5d32
.data 12800 bytes · 2.9% of section data
MD5 623855b3d19b63f6bf16f21d4483699f
.rsrc 1536 bytes · 0.3% of section data
MD5 80b36476b03226dd6224072701a67c19
.reloc 23040 bytes · 5.2% of section data
MD5 ddda495c8d45dad7935e95feed67365a

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 4695f9ad42320f33ccc917f674dff539.
  • 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.