PlayerFab Hijack Patch64.exe threat report

MD5 85d9b3245bc9ce0f183d22f1cf177880
Latest seen 2024-09-11 23:01:26 (2 years ago)
First seen 2024-09-11 23:01:26 (2 years ago)
Size 2 MB
Product PatchUi64

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Hack.Patcher. 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
Hack.Patcher
Recommended action
Scan and remove
Last analysis
2024-09-11 23:01:26 (2 years ago)
File hash
85d9b3245bc9ce0f183d22f1cf177880
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Hack.Patcher.

Timeline

First seen 2024-09-11 23:01:26 (2 years ago); latest analysis 2024-09-11 23:01:26 (2 years ago).

Publisher context

Company metadata: 飘云阁官方论坛. Product metadata: PatchUi64.

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.

PlayerFab Hijack Patch64.exe is a Windows file recorded in the ThreatInfo database. It is associated with PatchUi64. The reported company name is 飘云阁官方论坛. The current detection status is Hack.Patcher, based on the latest analysis from 2024-09-11 23:01:26 (2 years ago).

If PlayerFab Hijack Patch64.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 Hack.Patcher.

Product Name: PatchUi64
Company Name: 飘云阁官方论坛
MD5: 85d9b3245bc9ce0f183d22f1cf177880
Size: 2 MB
First Published: 2024-09-11 23:01:26 (2 years ago)
Latest Published: 2024-09-11 23:01:26 (2 years ago)
Status: Hack.Patcher (on last analysis)
Analysis Date: 2024-09-11 23:01:26 (2 years ago)
PlayerFab Hijack Patch64.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.

%programfiles%\dvdfab

ThreatInfo has observed PlayerFab Hijack Patch64.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 Germany 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 PlayerFab Hijack Patch64.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.

PlayerFab Hijack Patch64.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: 0x0004efec

PE Sections:

Name Size of data MD5
.text 403456 4e31df1098f847ad6496ef6b7adc528a
.rdata 89088 3f8ba8bcc96d0ea2acebba4556276d4e
.data 9216 cc38d5cea202b811a04d6abfc02176dc
.pdata 26112 73fa9d5b970c22c887fdb16e41d3f1bc
.rsrc 1842688 650a29f0299629e59568c8d9a55be79c
.reloc 7680 6817fc63240afee531e6ccae5a2d547f

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: