GridinSoft Threat Intelligence

29dc9261.rbf threat report

Detected as Adware.SweetIM File reputation report
MD5 42894025dcc53d2a9c2e2931d352f94b
Latest seen 2022-03-20 23:28:47 (4 years ago)
First seen 2017-05-26 13:02:40 (8 years ago)
Size 164 KB
Product hooking

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Adware.SweetIM. 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
Adware.SweetIM
Recommended action
Scan and remove
Last analysis
2022-03-20 23:28:47 (4 years ago)
File hash
42894025dcc53d2a9c2e2931d352f94b
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Adware.SweetIM.

Timeline

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

Publisher context

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

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. 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.

29dc9261.rbf is a Windows file recorded in the ThreatInfo database. It is associated with hooking. The reported company name is SweetIM Technologies Ltd.. The current detection status is Adware.SweetIM, based on the latest analysis from 2022-03-20 23:28:47 (4 years ago).

If 29dc9261.rbf 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 Adware.SweetIM.

Product Name: hooking
Company Name: SweetIM Technologies Ltd.
MD5: 42894025dcc53d2a9c2e2931d352f94b
Size: 164 KB
First Published: 2017-05-26 13:02:40 (8 years ago)
Latest Published: 2022-03-20 23:28:47 (4 years ago)
Status: Adware.SweetIM (on last analysis)
Analysis Date: 2022-03-20 23:28:47 (4 years ago)
29dc9261.rbf 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: SweetIM Technologies Ltd
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on 29dc9261.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

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

mghooking.dll 29dc9261.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.

Windows 7 40.0%
Windows 10 33.3%
Windows XP 20.0%
Windows Vista 6.7%

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

29dc9261.rbf is identified as pe for 32-bit 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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x000018ee
Image base 0x10000000

PE Sections:

Sections 8
Raw data 155648

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 4096 bytes · 2.6% of section data
MD5 bdf186bc9232350bc9938d7f6b02735c
CODE 118784 bytes · 76.3% of section data
MD5 6b2373f5980099235241b41c9592cef6
.rdata 8192 bytes · 5.3% of section data
MD5 bf47733e20d9d60459c0c5c25b590b57
.data 4096 bytes · 2.6% of section data
MD5 620f0b67a91f7f74151bc5be745b7110
DATA 4096 bytes · 2.6% of section data
MD5 1e113ae3a8df1185bf427664aba961c0
BSS 4096 bytes · 2.6% of section data
MD5 620f0b67a91f7f74151bc5be745b7110
.rsrc 4096 bytes · 2.6% of section data
MD5 1acd3f8b5107bc2c33a94857cd172909
.reloc 8192 bytes · 5.3% of section data
MD5 39aad0dc960de43366730cb9283f6c9e

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.

Report conclusion

GridinSoft detects this file as Adware.SweetIM

This report identifies 29dc9261.rbf by MD5 42894025dcc53d2a9c2e2931d352f94b. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 42894025dcc53d2a9c2e2931d352f94b.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found.