gptboot.efi threat report

MD5 0da32d491b0c6e537c5c7738678da4b2
Latest seen 2026-04-05 23:01:06 (a month ago)
First seen 2026-03-08 23:00:31 (2 months ago)
Size 107 KB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.ExtHeur!. 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.ExtHeur!
Recommended action
Scan and remove
Last analysis
2026-04-05 23:01:06 (a month ago)
File hash
0da32d491b0c6e537c5c7738678da4b2
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.ExtHeur!.

Timeline

First seen 2026-03-08 23:00:31 (2 months ago); latest analysis 2026-04-05 23:01:06 (a month ago).

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.

gptboot.efi is a Windows file recorded in the ThreatInfo database. The current detection status is Trojan.ExtHeur!, based on the latest analysis from 2026-04-05 23:01:06 (a month ago).

If gptboot.efi 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.ExtHeur!.

MD5: 0da32d491b0c6e537c5c7738678da4b2
Size: 107 KB
First Published: 2026-03-08 23:00:31 (2 months ago)
Latest Published: 2026-04-05 23:01:06 (a month ago)
Status: Trojan.ExtHeur! (on last analysis)
Analysis Date: 2026-04-05 23:01:06 (a month ago)
gptboot.efi 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%\somedownload\netgate-installer-v1.1.1-release-amd64.iso
%sysdrive%\somedownload\netgate-installer-v1.1.1-release-amd64.iso
%sysdrive%\somedownload\netgate-installer-v1.1.1-release-amd64.iso
%sysdrive%\somedownload\netgate-installer-v1.1.1-release-amd64.iso
%sysdrive%\somedownload\netgate-installer-v1.1.1-release-amd64.iso
%sysdrive%\somedownload\netgate-installer-v1.1.1-release-amd64.iso
%sysdrive%\somedownload\netgate-installer-v1.1.1-release-amd64.iso

ThreatInfo has observed gptboot.efi 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 United States 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 gptboot.efi 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.

gptboot.efi is identified as pe for 64 systems. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem:
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000000000000
Entry Address: 0x000026bc

PE Sections:

Name Size of data MD5
.text 24064 86d60b6d40e67e936e881079b92145bd
.data 82944 4c5e7ef10a9bdbff44414f70004cb691
.sdata 0 d41d8cd98f00b204e9800998ecf8427e
.dynamic 512 66f3505ad312d7439f510d577e341f91
.rela.dy 512 d03ea2b74380aaf9be88ff5d9c9a40fa
.reloc 512 0c45f6d812d079821c1d54c09ab89e1d
.dynsym 512 bf619eac0cdf3f68d496ea9344137e8b

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: