uxenstor.sys file report

MD5 18afb86d3a07d796be055e56abe9291b
Latest seen 2021-01-07 15:26:47 (5 years ago)
First seen 2020-10-27 17:01:00 (5 years ago)
Size 49 KB
Publisher uXen Project
Product uXen Storage
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:00 (5 years ago); latest analysis 2021-01-07 15:26:47 (5 years ago).

Publisher context

Company metadata: uXen Project. Product metadata: uXen Storage.

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.

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

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

uxenstor.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: 0x0000c064

PE Sections:

Name Size of data MD5
.text 20992 9c60162bc0e08805a5e5a39a037a33bb
.rdata 5632 97763039e517f4125ebbdd685ea81c7d
.data 3584 d008302b08fcfb91dff5f179b866743b
.pdata 512 da38e1e45a1b9278affdf1c10ed04090
INIT 1536 63167b45a8a0c4119a3c748294a13ba6
.rsrc 1536 dc1aeb644dda81177f4899e07861af43
.reloc 512 81283fed2dcd46ee49d80839876e7c18

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: