regedit.exe threat report

MD5 40a1fe88c4a1fd73d4f9bca89c32c05a
Latest seen 2025-03-16 23:01:52 (a year ago)
First seen 2021-07-06 20:38:14 (4 years ago)
Size 517 KB
Product Wine

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as General Threat. 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
General Threat
Recommended action
Scan and remove
Last analysis
2025-03-16 23:01:52 (a year ago)
File hash
40a1fe88c4a1fd73d4f9bca89c32c05a
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as General Threat.

Timeline

First seen 2021-07-06 20:38:14 (4 years ago); latest analysis 2025-03-16 23:01:52 (a year ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Wine.

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.

regedit.exe is a Windows file recorded in the ThreatInfo database. It is associated with Wine. The reported company name is Microsoft Corporation. The current detection status is General Threat, based on the latest analysis from 2025-03-16 23:01:52 (a year ago).

If regedit.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 General Threat.

Product Name: Wine
Company Name: Microsoft Corporation
MD5: 40a1fe88c4a1fd73d4f9bca89c32c05a
Size: 517 KB
First Published: 2021-07-06 20:38:14 (4 years ago)
Latest Published: 2025-03-16 23:01:52 (a year ago)
Status: General Threat (on last analysis)
Analysis Date: 2025-03-16 23:01:52 (a year ago)
regedit.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.

%windir%
%desktop%\playonmac.app.app\contents\resources\unix\wine\lib\wine
%desktop%\playonmac.app.app\contents\resources\unix\wine\lib\wine
%windir%
%sysdrive%\emulator\playonmac_4.3.4\playonmac\playonmac.app\contents\resources\unix\wine\lib\wine

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

80.0%
20.0%

The strongest geographic signal for this file is Israel with 80.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 7 80.0%
Windows 10 20.0%

The most common operating system signal for regedit.exe is Windows 7 with 80.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.

regedit.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: 0x10000000
Entry Address: 0x00001000

PE Sections:

Name Size of data MD5
.text 8 d1cdb50dfc28930120acdc4c14c7845d
.reloc 8 eace8829261e6e6b1c694d56a73bbdc0
.rsrc 528692 4d055069a358409d45bf74f6e429bf08

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: