reboot_launcher.exe threat report

MD5 0a99c1fbc2e19352240c29620e90ce32
Latest seen 2025-12-28 23:00:17 (5 months ago)
First seen 2025-12-27 23:01:23 (5 months ago)
Size 86 KB
Publisher com.example
Product reboot_launcher

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Adware.ELEX. 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
Adware.ELEX
Recommended action
Scan and remove
Last analysis
2025-12-28 23:00:17 (5 months ago)
File hash
0a99c1fbc2e19352240c29620e90ce32
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Adware.ELEX.

Timeline

First seen 2025-12-27 23:01:23 (5 months ago); latest analysis 2025-12-28 23:00:17 (5 months ago).

Publisher context

Company metadata: com.example. Product metadata: reboot_launcher.

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.

reboot_launcher.exe is a Windows file recorded in the ThreatInfo database. It is associated with reboot_launcher. The reported company name is com.example. The current detection status is Adware.ELEX, based on the latest analysis from 2025-12-28 23:00:17 (5 months ago).

If reboot_launcher.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 Adware.ELEX.

Product Name: reboot_launcher
Company Name: com.example
MD5: 0a99c1fbc2e19352240c29620e90ce32
Size: 86 KB
First Published: 2025-12-27 23:01:23 (5 months ago)
Latest Published: 2025-12-28 23:00:17 (5 months ago)
Status: Adware.ELEX (on last analysis)
Analysis Date: 2025-12-28 23:00:17 (5 months ago)
reboot_launcher.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.

%programfiles%
%programfiles%

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

reboot_launcher.exe 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: 0x0000000140000000
Entry Address: 0x00006070

PE Sections:

Name Size of data MD5
.text 24576 cf78317388f2faf333ca53d9234fb8d1
.rdata 16384 cbfcc47300e7290415a78ed8f69124a0
.data 1536 eb164699c91e65c424cec3015d7a65c7
.pdata 2048 79429b392e64d862cfd50c9e3baae859
.rsrc 42496 dcde81018ad428646b7cea2136c9970c
.reloc 512 20ced34586a201c755ea5c791d382efe

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: