GridinSoft Threat Intelligence

29B9.exe file report

Clean record File reputation report
MD5 732b4c64612774524083177348c1d295
Latest seen 2022-04-05 23:28:41 (4 years ago)
First seen 2022-04-05 23:28:41 (4 years ago)
Size 1 MB
Publisher Caqncuqn Instance
Product Uesnolzwwwhite

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-04-05 23:28:41 (4 years ago); latest analysis 2022-04-05 23:28:41 (4 years ago).

Publisher context

Company metadata: Caqncuqn Instance. Product metadata: Uesnolzwwwhite.

Digital signature

Signed by Microsoft Corporation. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

29B9.exe is a Windows file recorded in the ThreatInfo database. It is associated with Uesnolzwwwhite. The reported company name is Caqncuqn Instance. The current detection status is Clean, based on the latest analysis from 2022-04-05 23:28:41 (4 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Uesnolzwwwhite
Company Name: Caqncuqn Instance
MD5: 732b4c64612774524083177348c1d295
Size: 1 MB
First Published: 2022-04-05 23:28:41 (4 years ago)
Latest Published: 2022-04-05 23:28:41 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-04-05 23:28:41 (4 years ago)
Signed By: Microsoft Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%temp%

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

Windows 10 100.0%

The most common operating system signal for 29B9.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.

29B9.exe 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 0x00454000
Image base 0x00400000

PE Sections:

Sections 4
Raw data 199582

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

0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
512 bytes · 0.3% of section data
Uncommon name
MD5 db00f4a29861bd76e4bbb323075914f3
.rsrc 92675 bytes · 46.4% of section data
MD5 5c80ea0f5b4b0c3aa8afc1345a156797
106395 bytes · 53.3% of section data
Uncommon name
MD5 baf028c52b7c547ca05ffb07a1e101d7

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 732b4c64612774524083177348c1d295.
  • 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.