ZeroLauncher Generador.exe threat report

MD5 e205d72f381a485134ecceb282a7e330
Latest seen 2025-02-07 23:01:21 (a year ago)
First seen 2025-02-07 23:01:21 (a year ago)
Size 380 KB
Publisher Microsoft

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
2025-02-07 23:01:21 (a year ago)
File hash
e205d72f381a485134ecceb282a7e330
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2025-02-07 23:01:21 (a year ago); latest analysis 2025-02-07 23:01:21 (a year ago).

Publisher context

Company metadata: Microsoft. Product metadata: ZeroLauncher Generador.

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.

ZeroLauncher Generador.exe is a Windows file recorded in the ThreatInfo database. It is associated with ZeroLauncher Generador. The reported company name is Microsoft. The current detection status is Trojan.Heur!, based on the latest analysis from 2025-02-07 23:01:21 (a year ago).

If ZeroLauncher Generador.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: ZeroLauncher Generador
Company Name: Microsoft
MD5: e205d72f381a485134ecceb282a7e330
Size: 380 KB
First Published: 2025-02-07 23:01:21 (a year ago)
Latest Published: 2025-02-07 23:01:21 (a year ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2025-02-07 23:01:21 (a year ago)
ZeroLauncher Generador.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.

%sysdrive%\mu config\repack mu inarius\xtools\zerolauncher

ThreatInfo has observed ZeroLauncher Generador.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 Peru 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 ZeroLauncher Generador.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.

ZeroLauncher Generador.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: 0x00062000

.NET Info:

MVID: 66e40897-e47a-4c1a-9650-5f4fc0ebb324
Typelib ID: af0b239f-037b-4985-8f49-6511f46d17ed

PE Sections:

Name Size of data MD5
.text 196096 e5ae1f8aad2a1d71bb4c14fc9d928999
.sdata 512 8ba9accdbdb8619361e12a1b9f3ccc0f
.rsrc 174592 c95889494075cd83d40080a99706ac99
.reloc 512 7b2ee2a90a3912ba49e1495c7b9cbf81
†D+£u1 16896 8e7740a9cbdc35c63215a8576929cbc0

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: