DriverPack.exe threat 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

This report summarizes the file identity, detection status, publisher metadata, observed locations, and technical indicators for DriverPack.exe. ThreatInfo currently classifies this sample as PUP.DriverPack.

GridinSoft Anti-Malware detection

GridinSoft already detects this file

The latest ThreatInfo record shows DriverPack.exe detected as PUP.DriverPack. You can download GridinSoft Anti-Malware to scan the system and remove this detection if the file is present on your device.

Detection name
PUP.DriverPack
Last analysis
2022-11-16 23:01:34 (3 years ago)
File hash
0752a0bb3b4b55517bd7329a863b048c
Download Anti-Malware

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

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.

55.6%
11.1%
5.6%
5.6%
5.6%
5.6%
5.6%
5.6%

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

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

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x00001590

PE Sections:

Name Size of data MD5
.text 10752 12c8cad3692244bfd3e8dd029ca785da
.data 512 129df7189c5274dbd8fede9d9eab9071
.rdata 1024 912a92e85fa3a2e163dfc0efc5bc527e
/4 2560 4569d7be04ece0cd181c3cb09ff30eb6
.bss 0 00000000000000000000000000000000
.idata 2048 8a7664506d1584a29d6a60744c090613
.CRT 512 049bad4359f7e4531436d9264586a1c5
.tls 512 66b829fe22113d2979a56f04b6e9ef0d
.rsrc 214528 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.

More information: