PlayBoy-Extreme.exe threat report

MD5 659b7e86c6177a1ed7113784bd65eea9
Latest seen 2025-08-29 23:01:54 (9 months ago)
First seen 2025-08-29 23:01:54 (9 months ago)
Size 10 MB
Publisher Microsoft Windows
Product Runtime Broker

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
2025-08-29 23:01:54 (9 months ago)
File hash
659b7e86c6177a1ed7113784bd65eea9
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Sabsik.

Timeline

First seen 2025-08-29 23:01:54 (9 months ago); latest analysis 2025-08-29 23:01:54 (9 months ago).

Publisher context

Company metadata: Microsoft Windows. Product metadata: Runtime Broker.

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.

PlayBoy-Extreme.exe is a Windows file recorded in the ThreatInfo database. It is associated with Runtime Broker. The reported company name is Microsoft Windows. The current detection status is Ransom.Sabsik, based on the latest analysis from 2025-08-29 23:01:54 (9 months ago).

If PlayBoy-Extreme.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: Runtime Broker
Company Name: Microsoft Windows
MD5: 659b7e86c6177a1ed7113784bd65eea9
Size: 10 MB
First Published: 2025-08-29 23:01:54 (9 months ago)
Latest Published: 2025-08-29 23:01:54 (9 months ago)
Status: Ransom.Sabsik (on last analysis)
Analysis Date: 2025-08-29 23:01:54 (9 months ago)
PlayBoy-Extreme.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.

%profile%\downloads\freefire extreme

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

Windows 10 100.0%

The most common operating system signal for PlayBoy-Extreme.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.

PlayBoy-Extreme.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: 0x0000000140000000
Entry Address: 0x006fd9f0

PE Sections:

Name Size of data MD5
.text 7333376 2fdee9751fa7458e9bdd507008adccde
.rdata 1168896 7e04d7ab8c74b2baa2e4746dbbc66976
.data 1944576 4f879801d6504bcaa43fca898bd08552
.pdata 169472 62deb1a3e4816eb9cf7a7fe4cf982135
.rsrc 1536 25f9e4795915cf971e9b863b505e615c
.reloc 42496 de67e49480fd12007da694f2f773e518

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: