aJFdyjHN.exe threat report

MD5 1307e45cc5ed7481998eae67b4c88399
Latest seen 2023-09-05 23:04:11 (2 years ago)
First seen 2023-06-04 23:33:10 (2 years ago)
Size 6 MB
Publisher brother

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:04:11 (2 years ago)
File hash
1307e45cc5ed7481998eae67b4c88399
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Sabsik.

Timeline

First seen 2023-06-04 23:33:10 (2 years ago); latest analysis 2023-09-05 23:04:11 (2 years ago).

Publisher context

Company metadata: brother. Product metadata: brother brstswnd.

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.

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

If aJFdyjHN.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: brother brstswnd
Company Name: brother
MD5: 1307e45cc5ed7481998eae67b4c88399
Size: 6 MB
First Published: 2023-06-04 23:33:10 (2 years ago)
Latest Published: 2023-09-05 23:04:11 (2 years ago)
Status: Ransom.Sabsik (on last analysis)
Analysis Date: 2023-09-05 23:04:11 (2 years ago)
aJFdyjHN.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 aJFdyjHN.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%
%appdata%
%appdata%
%appdata%
%appdata%

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

80.0%
20.0%

The strongest geographic signal for this file is Uruguay with 80.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 aJFdyjHN.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.

aJFdyjHN.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: 0x013ba058

PE Sections:

Name Size of data MD5
1879040 8ab752d8f87ec4053d05667750c97652
84992 893c617351e01b7e2869267bdfd14234
2519552 6c4eb1f7f489bcd2c7885c70f371c223
8192 e6be31baa1a647cf32aa460ae07e05df
3584 f71c62e0e5cca2c2c153fe3acd4b98ba
.bss 0 d41d8cd98f00b204e9800998ecf8427e
512 2c5b0cf553d202f314a519f906ab18a9
512 e0ca88479731f8c157fbc82753838782
512 3250e3d29fb423d3896f36ec026a3c49
512 3f77fca8678a32f4edb25c1c27b50325
15872 9dad5dc0d2548a0ce425bdc690b1ab36
209408 05a09c72cf4f2919228eb7f03efc97b4
.edata 512 54548ba13dc9ca85ccc6d8326a2b0e5e
.idata 512 bc27d223c5ca40cac9ea24041e339b8e
.tls 512 9b96739993db85fcd7bad9adc2720f99
.rsrc 4608 83134d4a50e3d99779539ac77e6d6e45
.themida 0 d41d8cd98f00b204e9800998ecf8427e
.boot 1650688 892d50531b23da9e9d238d5b4b552214
.reloc 16 f3697ad6646e9698864910d949a317a2

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: