qG9bkB8P.exe threat report

MD5 fd59bd3d4746805751cfe6a936dd2845
Latest seen 2023-09-05 23:02:39 (2 years ago)
First seen 2023-09-05 23:02:39 (2 years ago)
Size 9 MB
Publisher egogim
Product ojekakor

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Ransom.Sabsik. 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
Ransom.Sabsik
Recommended action
Scan and remove
Last analysis
2023-09-05 23:02:39 (2 years ago)
File hash
fd59bd3d4746805751cfe6a936dd2845
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Sabsik.

Timeline

First seen 2023-09-05 23:02:39 (2 years ago); latest analysis 2023-09-05 23:02:39 (2 years ago).

Publisher context

Company metadata: egogim. Product metadata: ojekakor.

Digital signature

Signed by Logitech ZC-9015 USA State of Washington. 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.

qG9bkB8P.exe is a Windows file recorded in the ThreatInfo database. It is associated with ojekakor. The reported company name is egogim. The current detection status is Ransom.Sabsik, based on the latest analysis from 2023-09-05 23:02:39 (2 years ago).

If qG9bkB8P.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 Ransom.Sabsik.

Product Name: ojekakor
Company Name: egogim
MD5: fd59bd3d4746805751cfe6a936dd2845
Size: 9 MB
First Published: 2023-09-05 23:02:39 (2 years ago)
Latest Published: 2023-09-05 23:02:39 (2 years ago)
Status: Ransom.Sabsik (on last analysis)
Analysis Date: 2023-09-05 23:02:39 (2 years ago)
qG9bkB8P.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: Logitech ZC-9015 USA State of Washington
Status: Valid

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

%appdata%

ThreatInfo has observed qG9bkB8P.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 Uruguay 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 10 100.0%

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

qG9bkB8P.exe is identified as pe for 64 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: 64
Image Base: 0x0000000000400000
Entry Address: 0x011232b8

PE Sections:

Name Size of data MD5
2311680 6b0e0a7071991f0bd0449cfda017d2e5
106496 0eecd93f6fb590a25af6c945981a4a17
3276288 6f078d33ff39341afad65c6e39c60f4c
14848 a8e3b1c8464e87fa1ddd54dcac6f6d96
5120 8e9f9b09d90cec533cd61facccba341e
.bss 0 d41d8cd98f00b204e9800998ecf8427e
512 399e2ffe7411cb5de5d931b17f265455
512 b688697310e98956d37864e3094d926d
512 7cd02332cf08ad51776807381e899c1b
512 0d7175e3cfaba316d5d897e0fab53ba2
22016 53d97de8f1a638e7c4157e3bbebee48d
1192960 cb3134b959fa99c5a5bd9f044e6a5f97
.edata 512 4e4fa5640d9208d86865ff5068f20743
.idata 512 a63f22359f3e0777a24524c029514265
.tls 512 1601b901c60cfd7b7f3008e385460d76
.rsrc 144384 ffc9870132c2aad19ff23a3ad0be22fc
.themida 3276800 eebde761b83a04a480d2405e79a4465d
.reloc 16 b3a5e0e4cfe8502a3131a220fc4263b8

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: