uxennet.sys file report

MD5 f3c67fd9c62968b4d2396b341d48023f
Latest seen 2021-01-07 15:25:15 (5 years ago)
First seen 2020-10-27 17:01:12 (5 years ago)
Size 41 KB
Publisher uXen Project
Product uXen Network
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:12 (5 years ago); latest analysis 2021-01-07 15:25:15 (5 years ago).

Publisher context

Company metadata: uXen Project. Product metadata: uXen Network.

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.

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

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

uxennet.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: 0x00009290

PE Sections:

Name Size of data MD5
.text 11776 ad935afc63d62ce65f8a3365aafe3f06
.rdata 1536 83c2f1d96155136b0586f907e8941afe
.data 512 f56d1d5bed70f4f900ebe3191d55ec45
.pdata 1024 7ebb834d9e34a5e79790928e0c7499b5
PAGE 6144 4e738852c75b99a8b405030f8273d671
INIT 3072 d4716a23ba667c2ee0acf98e8bb50d0e
.rsrc 1536 67155d7e51dfe8968900cd4e0c3bfa8e
.reloc 512 a2d6bc2c505ec73e2666f707cb36476a

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: