uxendispdd.dll file report

MD5 609b6a75b2827016c708e3d276ed27aa
Latest seen 2021-01-07 15:27:56 (5 years ago)
First seen 2020-10-27 17:01:17 (5 years ago)
Size 33 KB
Publisher uXen Project
Product uXen Display
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:17 (5 years ago); latest analysis 2021-01-07 15:27:56 (5 years ago).

Publisher context

Company metadata: uXen Project. Product metadata: uXen Display.

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.

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

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

uxendispdd.dll 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: 0x00003510

PE Sections:

Name Size of data MD5
.text 11264 667c0f490715b84baef8501d334aa2bf
.rdata 1536 6412f7e316b88672901c6ab5aff0820f
.data 1024 7b7eaab6ab2ae794d39b662c4d06a729
.pdata 512 a71613613cd641c36e69890fe82a4c17
INIT 1024 e9988cd5a8a2326c476cf10558d7fcb1
.rsrc 1536 1abb49952b3f76e5dd88245cde81debe
.reloc 512 8e4ad7e6911f781e748cb4214ffac830

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: