uxenv4vguest.sys file report

MD5 1371df87bd34cf38b042287f863a238e
Latest seen 2021-01-07 15:27:01 (5 years ago)
First seen 2020-10-27 17:00:35 (5 years ago)
Size 29 KB
Publisher uXen Project
Product uXen V4V Guest
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:35 (5 years ago); latest analysis 2021-01-07 15:27:01 (5 years ago).

Publisher context

Company metadata: uXen Project. Product metadata: uXen V4V Guest.

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.

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

Product Name: uXen V4V Guest
Company Name: uXen Project
MD5: 1371df87bd34cf38b042287f863a238e
Size: 29 KB
First Published: 2020-10-27 17:00:35 (5 years ago)
Latest Published: 2021-01-07 15:27:01 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-07 15:27:01 (5 years ago)
Signed By: Bromium, Inc.
Status: Valid

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

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

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

25.0%
25.0%
25.0%
25.0%

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.

Windows 10 100.0%

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

uxenv4vguest.sys is identified as pe for 64 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.

Subsystem: Native
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000000010000
Entry Address: 0x000020f0

PE Sections:

Name Size of data MD5
.text 7680 33bec9fae422fa3bd0af81c81723d2fb
.rdata 1024 4cd95a8cb67b3de30c02280b2b91e0e7
.data 512 20f32a8ed9abca177603ff1d25be38f6
.pdata 512 7fec4a39334b7da56cddb5785294be5d
INIT 1536 970e7107fa5cee66c088c86b4fda9ffb
.rsrc 1536 94037b5ee9e5d8a09b2e5376e0c7c8b6
.reloc 512 861d50449c58d7f2a14e599767837c9e

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: