metin2client.exe threat report

MD5 9493d79bd60d031f781f62b711f4fe35
Latest seen 2026-04-06 23:01:15 (a month ago)
First seen 2026-04-06 23:01:15 (a month ago)
Size 31 MB
Publisher Ymir Entertainment
Product Metin2Client

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-04-06 23:01:15 (a month ago)
File hash
9493d79bd60d031f781f62b711f4fe35
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2026-04-06 23:01:15 (a month ago); latest analysis 2026-04-06 23:01:15 (a month ago).

Publisher context

Company metadata: Ymir Entertainment. Product metadata: Metin2Client.

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.

metin2client.exe is a Windows file recorded in the ThreatInfo database. It is associated with Metin2Client. The reported company name is Ymir Entertainment. The current detection status is Trojan.Heur!, based on the latest analysis from 2026-04-06 23:01:15 (a month ago).

If metin2client.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: Metin2Client
Company Name: Ymir Entertainment
MD5: 9493d79bd60d031f781f62b711f4fe35
Size: 31 MB
First Published: 2026-04-06 23:01:15 (a month ago)
Latest Published: 2026-04-06 23:01:15 (a month ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2026-04-06 23:01:15 (a month ago)
metin2client.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%

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

metin2client.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: 0x004822ef

PE Sections:

Name Size of data MD5
.text 24990720 19a3ddd684cf8368c9527cd96051958a
.rdata 2161664 67f6492a1243805dc474c3d19b424b52
.data 3112960 f5878be8826fceb1806fa99734c310a7
.data1 2560 3385b801c9e1463bf44bdfbe7db17fdf
.fptable 512 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 138240 9a34630e4bd4778ff8d08baaddeee33c
.reloc 2128896 86f95c5bbffa293f677e4c8caa825bc5

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: