1B64.exe threat report

MD5 b1e8d4d7dd26612c17eccbf66b280e7c
Latest seen 2024-02-13 23:42:47 (2 years ago)
First seen 2024-02-13 23:42:47 (2 years ago)
Size 6 MB
Publisher Acer Incorporated
Product Acer Collection

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
2024-02-13 23:42:47 (2 years ago)
File hash
b1e8d4d7dd26612c17eccbf66b280e7c
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Sabsik.

Timeline

First seen 2024-02-13 23:42:47 (2 years ago); latest analysis 2024-02-13 23:42:47 (2 years ago).

Publisher context

Company metadata: Acer Incorporated. Product metadata: Acer Collection.

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.

1B64.exe is a Windows file recorded in the ThreatInfo database. It is associated with Acer Collection. The reported company name is Acer Incorporated. The current detection status is Ransom.Sabsik, based on the latest analysis from 2024-02-13 23:42:47 (2 years ago).

If 1B64.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: Acer Collection
Company Name: Acer Incorporated
MD5: b1e8d4d7dd26612c17eccbf66b280e7c
Size: 6 MB
First Published: 2024-02-13 23:42:47 (2 years ago)
Latest Published: 2024-02-13 23:42:47 (2 years ago)
Status: Ransom.Sabsik (on last analysis)
Analysis Date: 2024-02-13 23:42:47 (2 years ago)
1B64.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.

%temp%

ThreatInfo has observed 1B64.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 Mexico 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 1B64.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.

1B64.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: 0x007e0b6d

PE Sections:

Name Size of data MD5
.text 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 0 d41d8cd98f00b204e9800998ecf8427e
.data 0 d41d8cd98f00b204e9800998ecf8427e
.vmpýÆ 0 d41d8cd98f00b204e9800998ecf8427e
.vmpýÆ 1024 6e5bae6c06da13a2f29aa4ba964fd145
.vmpýÆ 6492160 1c45f1d08c45b135accf5da8cbf0d7c4
.reloc 7168 56174fae3d66b72bf9ee754a71828b22
.rsrc 147456 9a7e8577e62d6b765c9b046db158f0ff

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: