DriverInstaller.x32.exe threat report

MD5 3ab56d91b0fd835d5cff1fc7059cf1b3
Latest seen 2026-02-21 23:00:41 (3 months ago)
First seen 2026-02-21 23:00:41 (3 months ago)
Size 693 KB
Publisher Auslogics

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as PUP.Auslogics. 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
PUP.Auslogics
Recommended action
Scan and remove
Last analysis
2026-02-21 23:00:41 (3 months ago)
File hash
3ab56d91b0fd835d5cff1fc7059cf1b3
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as PUP.Auslogics.

Timeline

First seen 2026-02-21 23:00:41 (3 months ago); latest analysis 2026-02-21 23:00:41 (3 months ago).

Publisher context

Company metadata: Auslogics. Product metadata: Driver Installer.

Digital signature

Signed by Auslogics Labs Pty Ltd. The signature is reported as valid, but signed files can still be bundled or abused.

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.

DriverInstaller.x32.exe is a Windows file recorded in the ThreatInfo database. It is associated with Driver Installer. The reported company name is Auslogics. The current detection status is PUP.Auslogics, based on the latest analysis from 2026-02-21 23:00:41 (3 months ago).

If DriverInstaller.x32.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 PUP.Auslogics.

Product Name: Driver Installer
Company Name: Auslogics
MD5: 3ab56d91b0fd835d5cff1fc7059cf1b3
Size: 693 KB
First Published: 2026-02-21 23:00:41 (3 months ago)
Latest Published: 2026-02-21 23:00:41 (3 months ago)
Status: PUP.Auslogics (on last analysis)
Analysis Date: 2026-02-21 23:00:41 (3 months ago)
DriverInstaller.x32.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.

Signed By: Auslogics Labs Pty Ltd
Status: Valid

The signature on DriverInstaller.x32.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%\auslogics

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

DriverInstaller.x32.exe is identified as pe for 32 systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x000a1838

PE Sections:

Name Size of data MD5
.text 652800 d2c8accea8b6ffb0de85915d4d95181a
.itext 3072 486249a6c1e8b12586c7f5ab2a531f8c
.data 10752 f236b3b02eaf272ff0cd244b3c250312
.bss 0 d41d8cd98f00b204e9800998ecf8427e
.idata 4096 4ff2d1cec405f5e96f2598fe617ad40a
.didata 512 714ddad234283341c9a83eb6f0c3d673
.edata 512 1598739e43f772be4e8ce83b23677622
.tls 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 0c820a7db4b54ba6ef25696a3377ea4c
.rsrc 12800 73d842ee4f3df345af662d19924b074a

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: