GridinSoft Threat Intelligence

wdtfuncU.ocx file report

Under review File reputation report
MD5 b1f765c5a1b323c515dee6d5057452eb
Latest seen 2022-08-15 23:16:18 (3 years ago)
First seen 2022-08-15 23:16:18 (3 years ago)
Size 542 KB
Publisher SAP, Walldorf
Signed by SAP SE

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-08-15 23:16:18 (3 years ago); latest analysis 2022-08-15 23:16:18 (3 years ago).

Publisher context

Company metadata: SAP, Walldorf. Product metadata: SAP GUI for Windows.

Digital signature

Signed by SAP SE. 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.

wdtfuncU.ocx is a Windows file recorded in the ThreatInfo database. It is associated with SAP GUI for Windows. The reported company name is SAP, Walldorf. The current detection status is Undefined, based on the latest analysis from 2022-08-15 23:16:18 (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: SAP GUI for Windows
Company Name: SAP, Walldorf
MD5: b1f765c5a1b323c515dee6d5057452eb
Size: 542 KB
First Published: 2022-08-15 23:16:18 (3 years ago)
Latest Published: 2022-08-15 23:16:18 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-15 23:16:18 (3 years ago)
Signed By: SAP SE
Status: Valid

The signature on wdtfuncU.ocx 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%\sap\frontend\sapgui

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

wdtfuncU.ocx 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 0x00047710
Image base 0x23120000

PE Sections:

Sections 5
Raw data 547840

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

.text 324096 bytes · 59.2% of section data
MD5 70566777fc8e90fc5e74fcd5ac71565a
.rdata 138240 bytes · 25.2% of section data
MD5 efedb7ce2414a6f0a9f56555d32fc69a
.data 7168 bytes · 1.3% of section data
MD5 7b07ecd2528fd85ee41f5387e3e91b6a
.rsrc 44544 bytes · 8.1% of section data
MD5 03a97296eccc2b22e323e3cc4a23a64f
.reloc 33792 bytes · 6.2% of section data
MD5 c250158a968cbb8d25f30d3543559e57

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