GridinSoft Threat Intelligence

driverscanner.exe file report

Under review File reputation report
MD5 6e7933c7ae9fe934399e15f0c78b4050
Latest seen 2023-08-10 23:22:37 (2 years ago)
First seen 2017-06-27 00:03:14 (8 years ago)
Size 7 MB
Publisher Uniblue Systems Ltd
Product DriverScanner
Signed by Uniblue Systems

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-06-27 00:03:14 (8 years ago); latest analysis 2023-08-10 23:22:37 (2 years ago).

Publisher context

Company metadata: Uniblue Systems Ltd . Product metadata: DriverScanner .

Digital signature

Signed by Uniblue Systems. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

File context

driverscanner.exe is a Windows file recorded in the ThreatInfo database. It is associated with DriverScanner . The reported company name is Uniblue Systems Ltd . The current detection status is Undefined, based on the latest analysis from 2023-08-10 23:22:37 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

File Details

Product Name: DriverScanner
Company Name: Uniblue Systems Ltd
MD5: 6e7933c7ae9fe934399e15f0c78b4050
Size: 7 MB
First Published: 2017-06-27 00:03:14 (8 years ago)
Latest Published: 2023-08-10 23:22:37 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-08-10 23:22:37 (2 years ago)

Overview

Signed By: Uniblue Systems
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on driverscanner.exe is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.

Common Places:

%localappdata%\setup wizard\632ed6dc-aeda-4b22-abcc-1aaef51f6b7a
%localappdata%\setup wizard\d9fcb2bd-bd50-463d-8f33-3973ec0a0a50
%localappdata%\setup wizard\164bba68-b3e9-4f30-9879-1c1bf883d9b3
%localappdata%\setup wizard\8e6f5dea-7c4f-42c8-8129-5e675c3d54d1
%localappdata%\setup wizard
%system%\config\systemprofile\appdata\local\setup wizard

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

Geographic signal

Observed country distribution

ThreatInfo has seen driverscanner.exe across 6 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Brazil
Share 38.9%
Low High activity

The strongest geographic signal for this file is Brazil with 38.9% 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 38.9%
Windows 7 38.9%
Windows 8.1 16.7%
Windows 8 5.6%

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

driverscanner.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 0x000113bc
Image base 0x00400000

PE Sections:

Sections 8
Raw data 169472

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

.text 61952 bytes · 36.6% of section data
MD5 3a126e478661f20816f9d9285615f98e
.itext 3072 bytes · 1.8% of section data
Uncommon name
MD5 ba48b9b17b3dd8b92da3bd93f20ddb34
.data 3584 bytes · 2.1% of section data
MD5 d7fd5f4b562d7961758f3d6a8c834fd0
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.idata 3584 bytes · 2.1% of section data
MD5 93d91a2b90e60bd758fc0c4908856ae1
.tls 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.rdata 512 bytes · 0.3% of section data
MD5 3dffc444ccc131c9dcee18db49ee6403
.rsrc 96768 bytes · 57.1% of section data
MD5 3c21b2f1457feaf2e61b64a3b694eed0

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

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 6e7933c7ae9fe934399e15f0c78b4050.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.