GridinSoft Threat Intelligence

wxmsw28u_core_vc_custom.dll file report

Under review File reputation report
MD5 a931cd9a11e4d89fe19e7851ee2ad4d8
Latest seen 2022-09-09 23:41:55 (3 years ago)
First seen 2022-09-09 23:41:55 (3 years ago)
Size 3 MB
Product wxWidgets

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-09-09 23:41:55 (3 years ago); latest analysis 2022-09-09 23:41:55 (3 years ago).

Publisher context

Company metadata: wxWidgets development team. Product metadata: wxWidgets.

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.

wxmsw28u_core_vc_custom.dll is a Windows file recorded in the ThreatInfo database. It is associated with wxWidgets. The reported company name is wxWidgets development team. The current detection status is Undefined, based on the latest analysis from 2022-09-09 23:41:55 (3 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: wxWidgets
Company Name: wxWidgets development team
MD5: a931cd9a11e4d89fe19e7851ee2ad4d8
Size: 3 MB
First Published: 2022-09-09 23:41:55 (3 years ago)
Latest Published: 2022-09-09 23:41:55 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-09-09 23:41:55 (3 years ago)
%commondir%\reallusion\postgresql

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

wxmsw28u_core_vc_custom.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00175fd8
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 3499520

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

.text 1617920 bytes · 46.2% of section data
MD5 cfac8fdca093fa4b7afeb1f56b29bdac
.rdata 1652736 bytes · 47.2% of section data
MD5 153fbb27f71d621c3e74763790f2e459
.data 43520 bytes · 1.2% of section data
MD5 5460493b3f2a4059365a54557259d103
.pdata 112128 bytes · 3.2% of section data
MD5 5d09b9d425e6c9a6484c13b0db9e8254
.rsrc 1536 bytes · 0.0% of section data
MD5 bee03d7d9d9361d390109247502f34b4
.reloc 71680 bytes · 2.0% of section data
MD5 d3ddfcb5fa6a99f1c8684d0774406c32

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