GridinSoft Threat Intelligence

wxbase30u_vc140_x64.dll file report

Under review File reputation report
MD5 a3b3d622a724b29fe1fd7f4f9cb48e7c
Latest seen 2024-06-02 23:01:10 (2 years ago)
First seen 2024-06-02 23:00:38 (2 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 2024-06-02 23:00:38 (2 years ago); latest analysis 2024-06-02 23:01:10 (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_x64.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-06-02 23:01:10 (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: a3b3d622a724b29fe1fd7f4f9cb48e7c
Size: 2 MB
First Published: 2024-06-02 23:00:38 (2 years ago)
Latest Published: 2024-06-02 23:01:10 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-06-02 23:01:10 (2 years ago)
%appdata%\nemetschek\vectorworks cloud services

ThreatInfo has observed wxbase30u_vc140_x64.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_x64.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_x64.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 0x00141d2c
Image base 0x0000000180000000

PE Sections:

Sections 8
Raw data 2602496

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

.text 1403904 bytes · 53.9% of section data
MD5 00befa510e30320294c4f5564b76bafa
.rdata 1072128 bytes · 41.2% of section data
MD5 357edbc757709c5712ac5c735fa0fc73
.data 40448 bytes · 1.6% of section data
MD5 b7540ad29fe34c0a18eca56ee24a9138
.pdata 74240 bytes · 2.9% of section data
MD5 6f912c5ea1106c387018db93ed99ed01
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 142f1b9c45440f01acbe103afca34420
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 1536 bytes · 0.1% of section data
MD5 584e925743882e0f6a94848fcddb6a46
.reloc 9216 bytes · 0.4% of section data
MD5 5f8124b06a376c3080d1715b7626b805

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