md1_1eaf.exe threat report

MD5 12ef159d590b06aa7673987b5b66df62
Latest seen 2025-02-19 23:00:50 (a year ago)
First seen 2021-10-22 20:36:58 (4 years ago)
Size 2 MB
Publisher TODO: <公司名>

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Agent. 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.Agent
Recommended action
Scan and remove
Last analysis
2025-02-19 23:00:50 (a year ago)
File hash
12ef159d590b06aa7673987b5b66df62
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Agent.

Timeline

First seen 2021-10-22 20:36:58 (4 years ago); latest analysis 2025-02-19 23:00:50 (a year ago).

Publisher context

Company metadata: TODO: <公司名>. Product metadata: TODO: <产品名>.

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.

md1_1eaf.exe is a Windows file recorded in the ThreatInfo database. It is associated with TODO: <产品名>. The reported company name is TODO: <公司名>. The current detection status is Trojan.Agent, based on the latest analysis from 2025-02-19 23:00:50 (a year ago).

If md1_1eaf.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.Agent.

Product Name: TODO: <产品名>
Company Name: TODO: <公司名>
MD5: 12ef159d590b06aa7673987b5b66df62
Size: 2 MB
First Published: 2021-10-22 20:36:58 (4 years ago)
Latest Published: 2025-02-19 23:00:50 (a year ago)
Status: Trojan.Agent (on last analysis)
Analysis Date: 2025-02-19 23:00:50 (a year ago)
md1_1eaf.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.

%temp%
%mydoc%
%programfiles%\company
%sysdrive%\system volume information\systemrestore\frstaging\users\pc\documents
%sysdrive%\system volume information\systemrestore\frstaging\program files (x86)\company
%localappdata%
%programfiles%\company
%programfiles%\company

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

25.0%
25.0%
12.5%
12.5%
12.5%
12.5%

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

Windows 10 62.5%
Windows 7 37.5%

The most common operating system signal for md1_1eaf.exe is Windows 10 with 62.5% 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.

md1_1eaf.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: 0x00001000

PE Sections:

Name Size of data MD5
.text 2066432 5b51e32ca2cefa5208a12a2ce2a2ebbe
.rsrc 165376 f1950091af71ff938d0979987f2e981f
.reloc 512 c2f765c3ec8794a39c79bc32b35bafe5

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: