setup[1].exe threat report

• » File
• File Details
• Overview
• Analysis

Analyst brief

What this report says

GridinSoft Anti-Malware detects setup[1].exe as Ransom.Sabsik. The sample was last observed on 2023-07-11 23:10:38 (2 years ago) / GoldenEgg.

This page combines the detection verdict with file identity, publisher metadata, alternate names, observed paths, geography, OS signals, and PE details so the report reads as a triage record rather than a standalone download page.

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-07-11 23:10:38 (2 years ago)

File hash

b59c8093621b9d5b5ad1905fab5aee00

Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Sabsik.

Timeline

First seen 2023-07-11 23:10:38 (2 years ago); latest analysis 2023-07-11 23:10:38 (2 years ago).

Publisher context

Product metadata: GoldenEgg.

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.

setup[1].exe is a Windows file recorded in the ThreatInfo database. It is associated with GoldenEgg. The current detection status is Ransom.Sabsik, based on the latest analysis from 2023-07-11 23:10:38 (2 years ago).

If setup[1].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.

File Details

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.

ThreatInfo has observed setup[1].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.

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

The most common operating system signal for setup[1].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.

Analysis

setup[1].exe 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.

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

This report identifies setup[1].exe by MD5 b59c8093621b9d5b5ad1905fab5aee00. 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 b59c8093621b9d5b5ad1905fab5aee00.
• 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.