26b4f1b5.rbf file report

MD5 08ebbfe17894a4f430aefb8e93cf7c72
Latest seen 2021-01-07 16:12:54 (5 years ago)
First seen 2018-02-13 17:10:57 (8 years ago)
Size 133 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-02-13 17:10:57 (8 years ago); latest analysis 2021-01-07 16:12:54 (5 years ago).

Publisher context

Company metadata: SlimWare Utilities, Inc.. Product metadata: SlimWare Uninstall Stub.

Digital signature

Signed by Slimware Utilities Holdings, Inc.. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

26b4f1b5.rbf is a Windows file recorded in the ThreatInfo database. It is associated with SlimWare Uninstall Stub. The reported company name is SlimWare Utilities, Inc.. The current detection status is Undefined, based on the latest analysis from 2021-01-07 16:12:54 (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: SlimWare Uninstall Stub
Company Name: SlimWare Utilities, Inc.
MD5: 08ebbfe17894a4f430aefb8e93cf7c72
Size: 133 KB
First Published: 2018-02-13 17:10:57 (8 years ago)
Latest Published: 2021-01-07 16:12:54 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-07 16:12:54 (5 years ago)
Signed By: Slimware Utilities Holdings, Inc.
Status: Valid

The signature on 26b4f1b5.rbf 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.

%programfiles%
%sysdrive%
%programfiles%
%programfiles%
%programfiles%

ThreatInfo has observed 26b4f1b5.rbf 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.

UninstallStub.exe
UninstallStub_IObitDel.exe
26b4f1b5.rbf

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

76.0%
16.0%
4.0%
4.0%

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

Windows 10 80.8%
Windows 8.1 11.5%
Windows 7 7.7%

The most common operating system signal for 26b4f1b5.rbf is Windows 10 with 80.8% 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.

26b4f1b5.rbf 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: 0x00004e37

PE Sections:

Name Size of data MD5
.text 75776 ab53513102350a1eb9db3be522b27a50
.rdata 26624 639e5f3dd91d3eec273dd13dbf3edcea
.data 5632 7a9cc27ec145d2bbce64fc7810a25894
.rsrc 8192 d9f8c2405f5a65223e123bd503032165
.reloc 5632 2c5136d11191bce4d0c39eeb0c247a73

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: