29dc9256.rbf file report

MD5 11dfc7ff30b9b44f1477989c8fff478f
Latest seen 2022-03-20 23:16:13 (4 years ago)
First seen 2017-05-26 13:02:45 (8 years ago)
Size 112 KB
Product SweetIM

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-26 13:02:45 (8 years ago); latest analysis 2022-03-20 23:16:13 (4 years ago).

Publisher context

Company metadata: SweetIM Technologies Ltd.. Product metadata: SweetIM.

Digital signature

Signed by SweetIM Technologies Ltd. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.

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.

29dc9256.rbf is a Windows file recorded in the ThreatInfo database. It is associated with SweetIM. The reported company name is SweetIM Technologies Ltd.. The current detection status is Undefined, based on the latest analysis from 2022-03-20 23:16:13 (4 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: SweetIM
Company Name: SweetIM Technologies Ltd.
MD5: 11dfc7ff30b9b44f1477989c8fff478f
Size: 112 KB
First Published: 2017-05-26 13:02:45 (8 years ago)
Latest Published: 2022-03-20 23:16:13 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-03-20 23:16:13 (4 years ago)
Signed By: SweetIM Technologies Ltd
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on 29dc9256.rbf is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.

%sysdrive%\adwcleaner\quarantine\files\iqamzodsaqbdgvdpaxfdhprkoxahjqou\messenger
%programfiles%\sweetim\messenger
%sysdrive%
%programfiles%\sweetim
%sysdrive%\terzo\programmi\sweetim
%sysdrive%\windows.old\program files (x86)\sweetim
%programfiles%\sweetim

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

SweetIM.exe
sweetim.exe
29dc9256.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.

21.1%
21.1%
15.8%
10.5%
5.3%
5.3%
5.3%
5.3%
5.3%
5.3%

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

Windows 7 47.4%
Windows 10 26.3%
Windows XP 21.1%
Windows Vista 5.3%

The most common operating system signal for 29dc9256.rbf is Windows 7 with 47.4% 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.

29dc9256.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: 0x00007e48

PE Sections:

Name Size of data MD5
.text 32768 66cac5fbd611e717180dcc8d3ab59217
.rdata 16384 023f8a980889074d9773d2dc68257149
.data 4096 21f9781d8964f763b5b5cc6cc4052443
.rsrc 49152 3cdcb3760e9a945909f1b93b799e26a2

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: