ubtorrent.dll file report

MD5 0b5bce0814e24d2fecd2e863ff0885c1
Latest seen 2026-01-01 23:01:22 (4 months ago)
First seen 2018-05-22 12:09:36 (7 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-05-22 12:09:36 (7 years ago); latest analysis 2026-01-01 23:01:22 (4 months ago).

Digital signature

Signed by IP Iaroslavskii Anton Andreevich. 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.

ubtorrent.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2026-01-01 23:01:22 (4 months 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.

MD5: 0b5bce0814e24d2fecd2e863ff0885c1
Size: 2 MB
First Published: 2018-05-22 12:09:36 (7 years ago)
Latest Published: 2026-01-01 23:01:22 (4 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-01-01 23:01:22 (4 months ago)
Signed By: IP Iaroslavskii Anton Andreevich
Status: Valid

The signature on ubtorrent.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%\ubar\ubar\modules
%commonappdata%\ubar (1)\ubar\modules
%commonappdata%\ubar\backup\ubar\modules
%sysdrive%\$recycle.bin\s-1-5-21-2032961536-1051169909-3059428775-1001\$rmazld2\ubar\modules
%sysdrive%\windows.old\programdata\ubar\ubar\modules
%sysdrive%\$recycle.bin\s-1-5-21-919011485-1044038557-1894674890-1000\$rje19wz\modules
%commonappdata%\~ubar\ubar\modules
%commonappdata%\ubar\ubar\modules
%commonappdata%\ubar\ubar\modules
%commonappdata%\ubar\ubar\modules

ThreatInfo has observed ubtorrent.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.

71.2%
13.7%
4.1%
1.8%
1.5%
1.3%
1.0%
0.8%
0.8%
0.5%
0.5%
0.5%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%

The strongest geographic signal for this file is Russian Federation with 71.2% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 67.3%
Windows 7 22.2%
Windows 8.1 9.3%
Windows Embedded 8.1 0.8%
Windows 8 0.5%

The most common operating system signal for ubtorrent.dll is Windows 10 with 67.3% 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.

ubtorrent.dll is identified as pe for 32 systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x001b7201

PE Sections:

Name Size of data MD5
.text 2217472 8ccb11c47cd4717bf2ce33b42dc0960f
.rdata 359936 3bfdd5cfa0056e0b22e9d76c81ad7028
.data 93184 3242ecbcc264bedc7c0fd6b338a8bba5
.gfids 4608 a0db0addc67ced52610baa6c484107b8
.tls 512 1f354d76203061bfdd5a53dae48d5435
.rsrc 1024 6a1d6b6c0f00135e210cedfb2fa64209
.reloc 101376 8104f874c4f7b8282d425dc0b800e5ec

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: