DriverUpdateHelper64.exe file report

MD5 3a640625ed568789f18d91071f8355ac
Latest seen 2024-01-15 23:48:11 (2 years ago)
First seen 2017-05-28 02:05:42 (8 years ago)
Size 269 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-28 02:05:42 (8 years ago); latest analysis 2024-01-15 23:48:11 (2 years ago).

Publisher context

Company metadata: WinZip Computing, S.L. (WinZip Computing). Product metadata: WinZip System Utilities Suite.

Digital signature

Signed by WinZip Computing LLC. 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.

DriverUpdateHelper64.exe is a Windows file recorded in the ThreatInfo database. It is associated with WinZip System Utilities Suite. The reported company name is WinZip Computing, S.L. (WinZip Computing). The current detection status is Undefined, based on the latest analysis from 2024-01-15 23:48:11 (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: WinZip System Utilities Suite
Company Name: WinZip Computing, S.L. (WinZip Computing)
MD5: 3a640625ed568789f18d91071f8355ac
Size: 269 KB
First Published: 2017-05-28 02:05:42 (8 years ago)
Latest Published: 2024-01-15 23:48:11 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-15 23:48:11 (2 years ago)
Signed By: WinZip Computing LLC
Status: Valid

The signature on DriverUpdateHelper64.exe 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%\winzip system utilities suite\updater\amd64helper
%programfiles%\winzip system utilities suite\updater
%programfiles%\winzip system utilities suite\updater
%programfiles%\winzip system utilities suite\updater
%programfiles%\winzip system utilities suite\updater

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

30.0%
10.0%
10.0%
10.0%
10.0%
10.0%
10.0%
10.0%

The strongest geographic signal for this file is United States with 30.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 63.6%
Windows 7 27.3%
Windows 8.1 9.1%

The most common operating system signal for DriverUpdateHelper64.exe is Windows 10 with 63.6% 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.

DriverUpdateHelper64.exe is identified as pe for 64 systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x00016384

PE Sections:

Name Size of data MD5
.text 157184 0a51bb09f41a374f7946ac1bf97ec8ed
.rdata 54784 9273b34acf52619d232952a94339f2bc
.data 11264 7d749afefacf271933ff08932cd71eef
.pdata 11776 c8131aee230cc0b119b3f0c62a834354
.rsrc 24064 e283fe250529d51c869ac61ec2f08414
.reloc 10240 0e796b96dd8ee4adf911a0156660487e

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.

More information: