GridinSoft Threat Intelligence

wxbase30u_vc140.dll file report

Under review File reputation report
MD5 1f68b7e923eeef3c7c1d87a643845f85
Latest seen 2024-07-07 23:02:18 (2 years ago)
First seen 2023-01-14 23:06:22 (3 years ago)
Size 2 MB
Product wxWidgets

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-01-14 23:06:22 (3 years ago); latest analysis 2024-07-07 23:02:18 (2 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.

wxbase30u_vc140.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 2024-07-07 23:02:18 (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: wxWidgets
Company Name: wxWidgets development team
MD5: 1f68b7e923eeef3c7c1d87a643845f85
Size: 2 MB
First Published: 2023-01-14 23:06:22 (3 years ago)
Latest Published: 2024-07-07 23:02:18 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-07-07 23:02:18 (2 years ago)
%programfiles%\ads

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

wxbase30u_vc140.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 0x001123e4
Image base 0x10000000

PE Sections:

Sections 7
Raw data 2102784

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

.text 1222656 bytes · 58.1% of section data
MD5 c6105d0523ef81d28204787863c4d17b
.rdata 761344 bytes · 36.2% of section data
MD5 608d3820118e0f5950beb80f8abd520a
.data 33792 bytes · 1.6% of section data
MD5 085cbd952c55b451a5a849d96decd653
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 2c4c3e130065678bf908eea7971fe396
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 1024 bytes · 0.0% of section data
MD5 8ced8583ac6d430a4fa70ab17e091828
.reloc 82944 bytes · 3.9% of section data
MD5 7e42575ac17fcdf05d81b41c6e034a40

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 1f68b7e923eeef3c7c1d87a643845f85.
  • 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.