DriverDoc.exe threat report

• » File
• File Details
• Overview
• Analysis

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

GridinSoft Anti-Malware detection

GridinSoft already detects this file

The latest ThreatInfo record shows DriverDoc.exe detected as PUP.Solvusoft. 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.Solvusoft

Last analysis

2024-01-21 23:10:32 (2 years ago)

File hash

3bd51ce1c5a0bf676acd51460ce11efc

Download Anti-Malware

DriverDoc.exe is a Windows file recorded in the ThreatInfo database. It is associated with DriverDoc. The reported company name is Solvusoft Corporation. The current detection status is PUP.Solvusoft, based on the latest analysis from 2024-01-21 23:10:32 (2 years ago).

If DriverDoc.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.Solvusoft.

File Details

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.

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

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

The most common operating system signal for DriverDoc.exe is Windows 8.1 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.

Analysis

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

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.