uxenvmlib.sys file report

MD5 981677e2d111b2a35894442e3455702a
Latest seen 2021-01-07 15:25:29 (5 years ago)
First seen 2020-10-27 17:02:07 (5 years ago)
Size 26 KB
Publisher uXen Project
Product uXen VM
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:02:07 (5 years ago); latest analysis 2021-01-07 15:25:29 (5 years ago).

Publisher context

Company metadata: uXen Project. Product metadata: uXen VM.

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.

uxenvmlib.sys is a Windows file recorded in the ThreatInfo database. It is associated with uXen VM. The reported company name is uXen Project. The current detection status is Undefined, based on the latest analysis from 2021-01-07 15:25:29 (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 VM
Company Name: uXen Project
MD5: 981677e2d111b2a35894442e3455702a
Size: 26 KB
First Published: 2020-10-27 17:02:07 (5 years ago)
Latest Published: 2021-01-07 15:25:29 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-07 15:25:29 (5 years ago)
Signed By: Bromium, Inc.
Status: Valid

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

uxenvmlib.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: 0x00008064

PE Sections:

Name Size of data MD5
.text 5632 c07317129736ca18cad9437c5b316e02
.rdata 1024 89d3693802a05da756a246fe30f16156
.data 512 043c46095689123e1f5be96c109c2f46
.pdata 512 33d47d5d681e57209d13000aabc64bdf
.shared 512 bf619eac0cdf3f68d496ea9344137e8b
.edata 512 618c67da127879e0c86f7c3b827c79e0
INIT 512 d94e5b35ad1b3a51687e538744cf2502
.rsrc 1024 a3b1c18171bbc05b785eec861604b945

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: