GridinSoft Threat Intelligence

DriverPack.exe threat report

Detected as PUP.DriverPack File reputation report
MD5 0752a0bb3b4b55517bd7329a863b048c
Latest seen 2022-11-16 23:01:34 (3 years ago)
First seen 2018-09-19 03:09:36 (7 years ago)
Size 235 KB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as PUP.DriverPack. 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.DriverPack
Recommended action
Scan and remove
Last analysis
2022-11-16 23:01:34 (3 years ago)
File hash
0752a0bb3b4b55517bd7329a863b048c
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as PUP.DriverPack, part of the PUP threat category.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2018-09-19 03:09:36 (7 years ago); latest analysis 2022-11-16 23:01:34 (3 years ago).

Publisher context

Product metadata: DriverPack Solution.

Digital signature

Signed by Kuzyakov Artur Vyacheslavovich IP. 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. 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. Review the PUP category for related samples and common context.

DriverPack.exe is a Windows file recorded in the ThreatInfo database. It is associated with DriverPack Solution. The current detection status is PUP.DriverPack, based on the latest analysis from 2022-11-16 23:01:34 (3 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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

Product Name: DriverPack Solution
MD5: 0752a0bb3b4b55517bd7329a863b048c
Size: 235 KB
First Published: 2018-09-19 03:09:36 (7 years ago)
Latest Published: 2022-11-16 23:01:34 (3 years ago)
Status: PUP.DriverPack (on last analysis)
Analysis Date: 2022-11-16 23:01:34 (3 years ago)
DriverPack.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: Kuzyakov Artur Vyacheslavovich IP
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on DriverPack.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.

%desktop%\new folder\beloffdp_2o18
%profile%\downloads\новая папка
%temp%\rar$exa3472.16491
%sysdrive%\$recycle.bin\.secure.\70043706
%desktop%\новая папка
%sysdrive%\закачка\новая папка (2)\beloff_2o18.1ol
%sysdrive%\программы\beloff 2019\beloff_2o19.2.1\beloff_2o19.2.1
%sysdrive%\download\beloff_2o18.1ol
%desktop%\beloff_2o19.6l
%profile%\downloads\beloffdp_2o2o.o5.5

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

Windows 10 61.1%
Windows 7 33.3%
Windows 8.1 5.6%

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

DriverPack.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 0x00001590
Image base 0x00400000

PE Sections:

Sections 9
Raw data 232448

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

.text 10752 bytes · 4.6% of section data
MD5 12c8cad3692244bfd3e8dd029ca785da
.data 512 bytes · 0.2% of section data
MD5 129df7189c5274dbd8fede9d9eab9071
.rdata 1024 bytes · 0.4% of section data
MD5 912a92e85fa3a2e163dfc0efc5bc527e
/4 2560 bytes · 1.1% of section data
Uncommon name
MD5 4569d7be04ece0cd181c3cb09ff30eb6
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.idata 2048 bytes · 0.9% of section data
MD5 8a7664506d1584a29d6a60744c090613
.CRT 512 bytes · 0.2% of section data
MD5 049bad4359f7e4531436d9264586a1c5
.tls 512 bytes · 0.2% of section data
MD5 66b829fe22113d2979a56f04b6e9ef0d
.rsrc 214528 bytes · 92.3% of section data
MD5 28945bd131ff554029b31e2d812ecd0c

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 PUP.DriverPack

This report identifies DriverPack.exe by MD5 0752a0bb3b4b55517bd7329a863b048c. It is part of the PUP report group. 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 0752a0bb3b4b55517bd7329a863b048c.
  • 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. Use the PUP category to compare similar reports.