uBar.exe threat report

MD5 74faab2a831b581ef82728261384f1a0
Latest seen 2023-05-04 23:18:43 (3 years ago)
First seen 2020-10-13 12:13:45 (5 years ago)
Size 13 MB
Publisher uBar
Product uBar

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as PUP.uBar. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
PUP.uBar
Recommended action
Scan and remove
Last analysis
2023-05-04 23:18:43 (3 years ago)
File hash
74faab2a831b581ef82728261384f1a0
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as PUP.uBar.

Timeline

First seen 2020-10-13 12:13:45 (5 years ago); latest analysis 2023-05-04 23:18:43 (3 years ago).

Publisher context

Company metadata: uBar. Product metadata: uBar.

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

uBar.exe is a Windows file recorded in the ThreatInfo database. It is associated with uBar. The reported company name is uBar. The current detection status is PUP.uBar, based on the latest analysis from 2023-05-04 23:18:43 (3 years ago).

If uBar.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as PUP.uBar.

Product Name: uBar
Company Name: uBar
MD5: 74faab2a831b581ef82728261384f1a0
Size: 13 MB
First Published: 2020-10-13 12:13:45 (5 years ago)
Latest Published: 2023-05-04 23:18:43 (3 years ago)
Status: PUP.uBar (on last analysis)
Analysis Date: 2023-05-04 23:18:43 (3 years ago)
uBar.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Signed By: IP Iaroslavskii Anton Andreevich
Status: Valid

The signature on uBar.exe 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
%commonappdata%\ubar
%commonappdata%\ubar
%commonappdata%\ubar
%commonappdata%\ubar

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

52.6%
26.3%
21.1%

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

Windows 10 73.7%
Windows 7 26.3%

The most common operating system signal for uBar.exe is Windows 10 with 73.7% 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.

uBar.exe 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: 0x00400000
Entry Address: 0x008cc238

PE Sections:

Name Size of data MD5
.text 9196544 a9de6da0c8067f51488e27c7987ee499
.itext 23040 4a349bb6b624153d09ddd7877384f35c
.data 199680 0cffcae857e1e071d47cf7ce395fe883
.bss 0 d41d8cd98f00b204e9800998ecf8427e
.idata 20992 db562575ca457d68165e19804d2d0e11
.didata 25600 4a6eb97cdbad29c78c53eb5a6e5e2e03
.edata 512 2dacece1362965c258b5fe2fbd337105
.tls 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 8a3de3705b5c642377b4d97af12733a4
.reloc 759808 96a99260cd9aecbcba3c72aa70d01e2b
.rsrc 3776000 de00498426426548ff228d51b2a1d3fd

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: