uxenmouse.sys file report

MD5 51f974a979f9db9b61aea89fd9a4984e
Latest seen 2021-01-07 15:33:40 (5 years ago)
First seen 2020-10-27 17:00:44 (5 years ago)
Size 24 KB
Publisher uXen Project
Product uXen Mouse
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:44 (5 years ago); latest analysis 2021-01-07 15:33:40 (5 years ago).

Publisher context

Company metadata: uXen Project. Product metadata: uXen Mouse.

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.

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

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

uxenmouse.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: 0x000013d0

PE Sections:

Name Size of data MD5
.text 2048 1fc876cd9153e2031d00fc798c1a4436
.rdata 1024 06b528a478428b4573b7c997c53fcea4
.data 512 6a3076c718c7d0e6db8bc522df0f23aa
.pdata 512 75d6d4ba9aab08baa892ccc6a5291118
PAGE 1536 5a438375a0545bf8d4b52d51669c09ac
INIT 1024 a198d291fc9467030b92fa30162ce726
.rsrc 1536 b2fca84872df6c40499b4698de9cdd85
.reloc 512 893bde0176f090710506ceb1c42b7cde

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: