GridinSoft Threat Intelligence

getuid.exe threat report

Detected as Trojan.Agent File reputation report
MD5 00bab554c9e525722c1fc73fd682bdea
Latest seen 2025-08-16 23:01:32 (9 months ago)
First seen 2018-08-10 06:09:17 (7 years ago)
Size 149 KB

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-08-16 23:01:32 (9 months ago)
File hash
00bab554c9e525722c1fc73fd682bdea
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Agent.

Timeline

First seen 2018-08-10 06:09:17 (7 years ago); latest analysis 2025-08-16 23:01:32 (9 months ago).

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

File context

getuid.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Trojan.Agent, based on the latest analysis from 2025-08-16 23:01:32 (9 months ago).

If getuid.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.

File Details

MD5: 00bab554c9e525722c1fc73fd682bdea
Size: 149 KB
First Published: 2018-08-10 06:09:17 (7 years ago)
Latest Published: 2025-08-16 23:01:32 (9 months ago)
Status: Trojan.Agent (on last analysis)
Analysis Date: 2025-08-16 23:01:32 (9 months ago)

Detection screenshot

getuid.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.

Common Places:

%sysdrive%\downloads\autodata 3.45 + crack full
%profile%\downloads\neuer ordner\autodata__3.45
%desktop%\desktop prin\autodata 3.45\autodata__3.45
%desktop%\2018\autodata 3.45(1)\autodata 3.45
%sysdrive%\изтеглени файлове\autodatacda
%sysdrive%\progz\autosoftware\autodata 3.45
%desktop%\razno\autodata\autodata 3.45
%desktop%\µtorrent downloads\autodata\autodata 3.45 + crack full [techtools.net]\autodata 3.45 + crack full [techtools.net]\autodata 3.45 + crack full [techtools.net]
%desktop%\razno\autodata\997me.autodata.3.45.full.included.part3.rar\autodata 3.45
%profile%\downloads\autodata\autodata_3.45

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

File Names:

2 observed names
GetUid-x86.exe getuid.exe

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Geography:

24 observed countries
10.0%
7.5%
7.5%
7.5%
7.5%
7.5%
5.0%
5.0%
5.0%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%
2.5%

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

OS Version:

Windows 10 70.0%
Windows 7 27.5%
Windows XP 2.5%

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

Analysis

getuid.exe is identified as pe for 32-bit 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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00001505
Image base 0x00400000

PE Sections:

Sections 6
Raw data 152064

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 21504 bytes · 14.1% of section data
MD5 d7d8168a49e31ca506c686d3dad73d33
.rdata 5632 bytes · 3.7% of section data
MD5 cde55ed30ce9199d7a5b3b222967457c
.data 2048 bytes · 1.3% of section data
MD5 7e5864b19283c31462a78c0750734cc1
.rsrc 75264 bytes · 49.5% of section data
MD5 aa6c2352714e41b681c6f38ee0fcb102
.vmp0 46592 bytes · 30.6% of section data
Uncommon name
MD5 b01efebb6afd577b04d776e4fe40253d
.vmp1 1024 bytes · 0.7% of section data
Uncommon name
MD5 96b7d2b2867787b0b69799a2cceb7f77

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.

Report conclusion

GridinSoft detects this file as Trojan.Agent

This report identifies getuid.exe by MD5 00bab554c9e525722c1fc73fd682bdea. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 00bab554c9e525722c1fc73fd682bdea.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found.