minhook.x64.dll threat report

MD5 6e2d50488e46545f4feaa17b2ba45c8b
Latest seen 2024-05-13 23:06:17 (2 years ago)
First seen 2024-05-13 23:06:17 (2 years ago)
Size 22 KB
Publisher Tsuda Kageyu
Product MinHook DLL

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Ransom.Zbot. 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.Zbot
Recommended action
Scan and remove
Last analysis
2024-05-13 23:06:17 (2 years ago)
File hash
6e2d50488e46545f4feaa17b2ba45c8b
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Zbot.

Timeline

First seen 2024-05-13 23:06:17 (2 years ago); latest analysis 2024-05-13 23:06:17 (2 years ago).

Publisher context

Company metadata: Tsuda Kageyu. Product metadata: MinHook DLL.

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.

minhook.x64.dll is a Windows file recorded in the ThreatInfo database. It is associated with MinHook DLL. The reported company name is Tsuda Kageyu. The current detection status is Ransom.Zbot, based on the latest analysis from 2024-05-13 23:06:17 (2 years ago).

If minhook.x64.dll 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.Zbot.

Product Name: MinHook DLL
Company Name: Tsuda Kageyu
MD5: 6e2d50488e46545f4feaa17b2ba45c8b
Size: 22 KB
First Published: 2024-05-13 23:06:17 (2 years ago)
Latest Published: 2024-05-13 23:06:17 (2 years ago)
Status: Ransom.Zbot (on last analysis)
Analysis Date: 2024-05-13 23:06:17 (2 years ago)
minhook.x64.dll 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%\hive\windows_coc_tw_pc
%programfiles%\hive\windows_coc_tw_pc

ThreatInfo has observed minhook.x64.dll 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 Hong Kong 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 minhook.x64.dll 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.

minhook.x64.dll 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: 0x0000000180000000
Entry Address: 0x00003510

PE Sections:

Name Size of data MD5
.text 12288 9c491000ff6b3baaeda67050600adf52
.rdata 5632 3638ed0526b7a0b2b83cb9d334721ae1
.data 1024 605d38215bd8f1c4c0884fd242316590
.pdata 1024 38b1894787bf97ba5c7d2a9bc5168e3f
.rsrc 1536 509bbab6b814781c28e691b129102a1b
.reloc 512 e1378a5b578a7b4da405c9acdfbd7d0b

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: