GridinSoft Threat Intelligence

RegMan.dll file report

Under review File reputation report
MD5 199086906011bf77e0a00370d2f76a30
Latest seen 2021-01-14 13:53:06 (5 years ago)
First seen 2021-01-14 13:53:06 (5 years ago)
Size 68 KB
Product RegMan.dll

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-14 13:53:06 (5 years ago); latest analysis 2021-01-14 13:53:06 (5 years ago).

Publisher context

Product metadata: RegMan.dll.

Digital signature

Signed by Blue Century Software 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.

RegMan.dll is a Windows file recorded in the ThreatInfo database. It is associated with RegMan.dll. The current detection status is Undefined, based on the latest analysis from 2021-01-14 13:53:06 (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: RegMan.dll
MD5: 199086906011bf77e0a00370d2f76a30
Size: 68 KB
First Published: 2021-01-14 13:53:06 (5 years ago)
Latest Published: 2021-01-14 13:53:06 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-14 13:53:06 (5 years ago)
Signed By: Blue Century Software Co., Ltd
Status: Valid

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

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

RegMan.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 0x00002640
Image base 0x10000000

PE Sections:

Sections 6
Raw data 53248

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

.text 31744 bytes · 59.6% of section data
MD5 3427e30df2d3938223a844c2d10cedab
.rdata 15360 bytes · 28.8% of section data
MD5 55c45e24d9d7d74b11accf31a753b610
.data 512 bytes · 1.0% of section data
MD5 b3cf11cf80b2dc189bac802db63b4a8f
.CRT 512 bytes · 1.0% of section data
MD5 902b359c28231898eb096cc11db661a5
.rsrc 1536 bytes · 2.9% of section data
MD5 3835176c9eb8b501fa641979ce2a0e0a
.reloc 3584 bytes · 6.7% of section data
MD5 80d1a0fb35c54bdf9ac0e57d5a1a3c62

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 199086906011bf77e0a00370d2f76a30.
  • 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.