Driverpack

Category: pua · Aliases: None known · Sample count (EMBER 2018): 326 · Enrichment: expert-seo · Updated: 2026-06-09

Overview

Adware:Win32/Driverpack (often branded as DriverPack Solution) is an intrusive Potentially Unwanted Application (PUA) family that masquerades as a legitimate system utility for updating hardware drivers.

Understanding Driverpack
To the average user, Driverpack presents itself as a helpful tool to fix computer errors. For incident responders, it is a deceptive monetization scheme and a massive security liability. While it may occasionally install legitimate (albeit often outdated) drivers, its primary purpose is to bundle massive amounts of third-party adware, toolbars, and search hijackers onto the endpoint during the installation process.

Execution and Evasion Strategies
Driverpack is downloaded voluntarily by users seeking hardware fixes or bundled with other freeware. The execution is characterized by deceptive UI tactics (Dark Patterns). Unless the user explicitly selects 'Expert Mode' and unchecks dozens of hidden boxes, Driverpack will silently install affiliated software. It establishes deep persistence by dropping services and scheduled tasks to initiate daily 'scans'. Furthermore, Driverpack frequently disables UAC and alters Windows Security Center settings to prevent the OS from blocking its unsigned driver installations.

Indicators of Compromise (IoCs)
The impact is a severely bloated endpoint, compromised search privacy, and extreme system instability (BSODs) caused by forcefully installed, incompatible drivers. Threat hunters will observe a massive spike in outbound HTTP connections to affiliate tracking networks. The Windows Registry will show heavy modifications under HKCU\Software. EDR tools often flag the software for attempting to load unsigned kernel-mode drivers.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

TechniqueNameTactic
T1189Drive-by CompromiseInitial Access
T1204.002User Execution: Malicious FileExecution
T1562.001Impair Defenses: Disable or Modify ToolsDefense Evasion
T1053.005Scheduled Task/Job: Scheduled TaskPersistence
T1112Modify RegistryDefense Evasion

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_DRIVERPACK {
    meta:
        description = "Detects Driverpack (pua)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "driverpack" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Driverpack Activity
id: a4cea0fe43c8c1201e7ae978761676ec
status: experimental
description: Detects generic indicators of the driverpack malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*driverpack*"
    condition: selection
level: medium

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Quarantine the endpoint to halt the ongoing downloading of secondary adware modules and potentially incompatible drivers.
  2. Audit the 'Add/Remove Programs' list and methodically uninstall the Driverpack utility and all software installed concurrently.
  3. Utilize the Windows System Restore feature to roll back the registry and drivers to a state prior to the Driverpack installation.
  4. Deploy specialized adware removal tools (like AdwCleaner) to identify and strip deep registry hooks left by the bundled PUPs.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not allow users to use third-party driver updaters; enforce strict policies requiring drivers to be sourced only from official OEM websites.
  2. Avoid ignoring the installation; the forced installation of incorrect or unsigned drivers can permanently corrupt the operating system.

References & External Analysis

Related Families (Category: pua)

Explore other malware families in the same category:

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/driverpack.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Replit, StackBlitz, CodeSandbox, and CodePen.