chr.exe threat report

MD5 e0e00d22cd20295a447f3ea8b05070ef
Latest seen 2023-07-26 23:51:43 (2 years ago)
First seen 2023-07-26 23:51:43 (2 years ago)
Size 452 KB
Product Hipbear
Signed by Shan Feng

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Adware.ELEX. 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.ELEX
Recommended action
Scan and remove
Last analysis
2023-07-26 23:51:43 (2 years ago)
File hash
e0e00d22cd20295a447f3ea8b05070ef
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Adware.ELEX.

Timeline

First seen 2023-07-26 23:51:43 (2 years ago); latest analysis 2023-07-26 23:51:43 (2 years ago).

Publisher context

Product metadata: Hipbear.

Digital signature

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

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.

chr.exe is a Windows file recorded in the ThreatInfo database. It is associated with Hipbear. The current detection status is Adware.ELEX, based on the latest analysis from 2023-07-26 23:51:43 (2 years ago).

If chr.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 Adware.ELEX.

Product Name: Hipbear
MD5: e0e00d22cd20295a447f3ea8b05070ef
Size: 452 KB
First Published: 2023-07-26 23:51:43 (2 years ago)
Latest Published: 2023-07-26 23:51:43 (2 years ago)
Status: Adware.ELEX (on last analysis)
Analysis Date: 2023-07-26 23:51:43 (2 years ago)
chr.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: Shan Feng
Status: Invalid (digital signature could be stolen or file could be patched)

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

%appdata%\qksee\update\qks_update_v3.3.1.exe

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

100.0%

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

Windows 8 100.0%

The most common operating system signal for chr.exe is Windows 8 with 100.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.

chr.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: 0x00033b1b

PE Sections:

Name Size of data MD5
.text 338944 28678f4c6a078dab2bae938a409f39cd
.rdata 92672 62eca97fbefbd145bad140a5e5c03eea
.data 7680 f5dfdec34dad56795a0574ba88dbf131
.gfids 1024 4cc26e160e88ddd4057e2b46e3fbb8ab
.tls 512 1f354d76203061bfdd5a53dae48d5435
.rsrc 16896 b47637be479ed85af94331beab395772

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: