GridinSoft Threat Intelligence

ConfigCenter.dll file report

Under review File reputation report
MD5 2bc1a4d540ab92087d6cb25f4a2e60ec
Latest seen 2023-12-06 23:32:53 (2 years ago)
First seen 2023-12-06 23:32:53 (2 years ago)
Size 758 KB
Product ConfigCenter

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-12-06 23:32:53 (2 years ago); latest analysis 2023-12-06 23:32:53 (2 years ago).

Publisher context

Product metadata: ConfigCenter.

Digital signature

Signed by Chengdu Qilu 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 ConfigCenter. The current detection status is Undefined, based on the latest analysis from 2023-12-06 23:32:53 (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: ConfigCenter
MD5: 2bc1a4d540ab92087d6cb25f4a2e60ec
Size: 758 KB
First Published: 2023-12-06 23:32:53 (2 years ago)
Latest Published: 2023-12-06 23:32:53 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-12-06 23:32:53 (2 years ago)
Signed By: Chengdu Qilu 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

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 100.0%

The most common operating system signal for ConfigCenter.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.

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 0x000514f3
Image base 0x10000000

PE Sections:

Sections 5
Raw data 768512

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

.text 569344 bytes · 74.1% of section data
MD5 86ea10cae2260382bdf63a6110a62a3b
.rdata 154112 bytes · 20.1% of section data
MD5 99a7061a64b387abcc2633855f48d469
.data 15360 bytes · 2.0% of section data
MD5 8968ff6c5bd75d94db7da04dfeffbc34
.rsrc 1536 bytes · 0.2% of section data
MD5 3132851b9d885d24ad91478f6df1ce68
.reloc 28160 bytes · 3.7% of section data
MD5 5cf866b98c3ef1880dfd59f0b02b11c6

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 2bc1a4d540ab92087d6cb25f4a2e60ec.
  • 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.