mplayerc.exe threat report

MD5 fc7a1129fb7ce6f7d04c6fef73f2ae17
Latest seen 2026-01-15 23:01:22 (4 months ago)
First seen 2026-01-15 23:01:21 (4 months ago)
Size 5 MB
Publisher Gabest

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. 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
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2026-01-15 23:01:22 (4 months ago)
File hash
fc7a1129fb7ce6f7d04c6fef73f2ae17
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2026-01-15 23:01:21 (4 months ago); latest analysis 2026-01-15 23:01:22 (4 months ago).

Publisher context

Company metadata: Gabest. Product metadata: Media Player Classic.

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.

mplayerc.exe is a Windows file recorded in the ThreatInfo database. It is associated with Media Player Classic. The reported company name is Gabest. The current detection status is Trojan.Heur!, based on the latest analysis from 2026-01-15 23:01:22 (4 months ago).

If mplayerc.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 Trojan.Heur!.

Product Name: Media Player Classic
Company Name: Gabest
MD5: fc7a1129fb7ce6f7d04c6fef73f2ae17
Size: 5 MB
First Published: 2026-01-15 23:01:21 (4 months ago)
Latest Published: 2026-01-15 23:01:22 (4 months ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2026-01-15 23:01:22 (4 months ago)
mplayerc.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.

%desktop%\mac\m1 pro\work\wh\2021\tech info films\man & b&w instructional videos
%desktop%\mac\m1 pro\work\wh\2021\tech info films\man & b&w instructional videos

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

mplayerc.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: 0x002b40d2

PE Sections:

Name Size of data MD5
.text 3371008 808ec3ac0efcd99cd497c0759abe42d0
_TEXT64 4096 d1e253312bfcd69470aa9eedc9228d17
.rdata 970752 1b0857a9c581310e0dbd9cd5af1dab3e
.data 266240 15ce92033093cbd1dc6db04c6fdba473
.rsrc 1212416 5f4f55d817686dbae84e92038188beb7

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: