GridinSoft Threat Intelligence

uxenpatcher.exe file report

Under review File reputation report
MD5 0f76a5df5afc9f3847a7fd9fe1ff001e
Latest seen 2021-01-07 15:25:10 (5 years ago)
First seen 2020-10-27 17:00:53 (5 years ago)
Size 61 KB
Signed by Bromium, Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-10-27 17:00:53 (5 years ago); latest analysis 2021-01-07 15:25:10 (5 years ago).

Digital signature

Signed by Bromium, Inc.. 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.

File context

uxenpatcher.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-01-07 15:25:10 (5 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.

File Details

MD5: 0f76a5df5afc9f3847a7fd9fe1ff001e
Size: 61 KB
First Published: 2020-10-27 17:00:53 (5 years ago)
Latest Published: 2021-01-07 15:25:10 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-07 15:25:10 (5 years ago)

Overview

Signed By: Bromium, Inc.
Status: Valid

The signature on uxenpatcher.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.

Common Places:

%commonappdata%\bromium\vsentry\4.2.2.1946\stage1\stage1image0004\atomictemplatedata
%commonappdata%\bromium\vsentry\4.2.2.1946\stage1\stage1image0003\atomictemplatedata

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

Geographic signal

Observed country distribution

ThreatInfo has seen uxenpatcher.exe across 4 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Belgium
Share 25.0%
Low High activity

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

OS Version:

Windows 10 100.0%

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

Analysis

uxenpatcher.exe is identified as pe for 64-bit 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.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x000014f0
Image base 0x0000000000400000

PE Sections:

Sections 12
Raw data 46592

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

.text 29696 bytes · 63.7% of section data
MD5 c22cb36aefb32e41a1a102a3734ef882
.data 512 bytes · 1.1% of section data
MD5 144dfb254d36ee4cc9e35c57025d793e
.rdata 6144 bytes · 13.2% of section data
MD5 a4f0bacac0b9dfd07c822c9fac0369df
.buildid 512 bytes · 1.1% of section data
Uncommon name
MD5 cdeadbe3de5370f4be27a258b65c7165
.pdata 2048 bytes · 4.4% of section data
MD5 e8062c02da432db73a3a81a6a56560d2
.xdata 1536 bytes · 3.3% of section data
Uncommon name
MD5 2c6b3fb74237f42ee6392b7d5330c1f2
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.edata 512 bytes · 1.1% of section data
MD5 491bb63cdcb1af491a1e52deac19f262
.idata 4096 bytes · 8.8% of section data
MD5 d15cc51c9b5f2a4b305f00bcb8fa2871
.CRT 512 bytes · 1.1% of section data
MD5 c04cd530db15f81508c8d96bafb84e65
.tls 512 bytes · 1.1% of section data
MD5 67edc550f7c10a1ccf56dfe34ceceab4
.reloc 512 bytes · 1.1% of section data
MD5 a8b2d70d5f1412fe9b603a05127e947c

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 0f76a5df5afc9f3847a7fd9fe1ff001e.
  • 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.