GridinSoft Threat Intelligence

uxenv4vlib.sys file report

Under review File reputation report
MD5 09c3b5d59798eada1f5400d63634ef2d
Latest seen 2021-01-07 15:33:03 (5 years ago)
First seen 2020-10-27 17:01:55 (5 years ago)
Size 75 KB
Publisher HP
Product uXen Hypervisor
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:01:55 (5 years ago); latest analysis 2021-01-07 15:33:03 (5 years ago).

Publisher context

Company metadata: HP. Product metadata: uXen Hypervisor.

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

uxenv4vlib.sys is a Windows file recorded in the ThreatInfo database. It is associated with uXen Hypervisor. The reported company name is HP. The current detection status is Undefined, based on the latest analysis from 2021-01-07 15:33:03 (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

Product Name: uXen Hypervisor
Company Name: HP
MD5: 09c3b5d59798eada1f5400d63634ef2d
Size: 75 KB
First Published: 2020-10-27 17:01:55 (5 years ago)
Latest Published: 2021-01-07 15:33:03 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-07 15:33:03 (5 years ago)

Overview

Signed By: Bromium, Inc.
Status: Valid

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

uxenv4vlib.sys is identified as pe for 64-bit systems. The subsystem is Native. 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 Native
Entry point 0x00012008
Image base 0x0000000000010000

PE Sections:

Sections 10
Raw data 60928

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

.text 39936 bytes · 65.5% of section data
MD5 b1d7c65675fd99f4c87e173be87dd6da
.rdata 4096 bytes · 6.7% of section data
MD5 b8dea5f7fefa2612e54b7deac71fea04
.data 1024 bytes · 1.7% of section data
MD5 34dba2bf46c54552f1328d950668cc9b
.pdata 2048 bytes · 3.4% of section data
MD5 11622cbe59f31c11caf6463d912a8541
.gfids 512 bytes · 0.8% of section data
Uncommon name
MD5 64d1f04ee674327483852f238bb2c4a5
PAGE 7168 bytes · 11.8% of section data
Uncommon name
MD5 ccc30180845e37c3bce279f38e145f20
.edata 1536 bytes · 2.5% of section data
MD5 cbb49182f941ac8840150df785bac03a
INIT 3072 bytes · 5.0% of section data
Uncommon name
MD5 06ebfb0d9fcd3af9855038dee124a68c
.rsrc 1024 bytes · 1.7% of section data
MD5 9f2c619fa1480be502484815dc875c28
.reloc 512 bytes · 0.8% of section data
MD5 7c777b9b2bb4fac56115de9d55d70abb

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 09c3b5d59798eada1f5400d63634ef2d.
  • 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.