Windows Update.exe threat report

MD5 b33429311a94ce5b22a5cc4ded8c70bf
Latest seen 2021-06-20 20:14:45 (4 years ago)
First seen 2021-06-20 20:14:45 (4 years ago)
Size 393 KB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Adware.Adware. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Adware.Adware
Recommended action
Scan and remove
Last analysis
2021-06-20 20:14:45 (4 years ago)
File hash
b33429311a94ce5b22a5cc4ded8c70bf
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Adware.Adware.

Timeline

First seen 2021-06-20 20:14:45 (4 years ago); latest analysis 2021-06-20 20:14:45 (4 years ago).

Publisher context

Company metadata: Windows_Explorer_CID_aJ64E4ZVKuhyUKqu. Product metadata: Windows_Explorer_CID_aJ64E4ZVKuhyUKqu.

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

Windows Update.exe is a Windows file recorded in the ThreatInfo database. It is associated with Windows_Explorer_CID_aJ64E4ZVKuhyUKqu. The reported company name is Windows_Explorer_CID_aJ64E4ZVKuhyUKqu. The current detection status is Adware.Adware, based on the latest analysis from 2021-06-20 20:14:45 (4 years ago).

If Windows Update.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Adware.Adware.

Product Name: Windows_Explorer_CID_aJ64E4ZVKuhyUKqu
Company Name: Windows_Explorer_CID_aJ64E4ZVKuhyUKqu
MD5: b33429311a94ce5b22a5cc4ded8c70bf
Size: 393 KB
First Published: 2021-06-20 20:14:45 (4 years ago)
Latest Published: 2021-06-20 20:14:45 (4 years ago)
Status: Adware.Adware (on last analysis)
Analysis Date: 2021-06-20 20:14:45 (4 years ago)
Windows Update.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%programfiles%

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

100.0%

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

Windows 10 100.0%

The most common operating system signal for Windows Update.exe 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.

Windows Update.exe is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x0006220e

.NET Info:

MVID: 29c73957-66eb-4421-b3f2-55b38eded3c4

PE Sections:

Name Size of data MD5
.text 394240 5cb685120ed8dd1193991f3057f7d625
.rsrc 7168 1ecc639e5dff2f5f59f2ea28443a7f7a
.reloc 512 a283e370cfea9ebec4adfecd3d148beb

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: