Information about drivermax.exe
drivermax.exe
drivermax.exe is a Windows file recorded in the ThreatInfo database. It is associated with DriverMax. The reported company name is Innovative Solutions. The current detection status is Undefined, based on the latest analysis from 2022-02-17 23:57:29 (4 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: | DriverMax |
| Company Name: | Innovative Solutions |
| MD5: | 79a426862d3f35a2c2cd879661bd1eca |
| Size: | 7 MB |
| First Published: | 2020-06-16 22:09:03 (5 years ago) |
| Latest Published: | 2022-02-17 23:57:29 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2022-02-17 23:57:29 (4 years ago) |
Common Places:
| %profile%\downloads\programs\drivermax.pro.11.17.0.35.portable\app |
| %sysdrive%\todo en 1\programas\programa portable\driver\drivermax.pro.11.17.0.35.portable.rar\drivermax.pro.11.17.0.35.portable\drivermax\app |
ThreatInfo has observed drivermax.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.
Geography:
| 66.7% | ||
| 33.3% |
The strongest geographic signal for this file is Iran, Islamic Republic of with 66.7% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
| Windows 8.1 | 66.7% | |
| Windows 10 | 33.3% |
The most common operating system signal for drivermax.exe is Windows 8.1 with 66.7% 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
drivermax.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: | 0x0027be04 |
PE Sections:
| Name | Size of data | MD5 |
| CODE | 2607104 | febdecaad96600dcfdf37dd4d722c8be |
| DATA | 34304 | 8132bc70b9ebee0afdd5e92a77ce8d29 |
| BSS | 0 | 00000000000000000000000000000000 |
| .idata | 16384 | ccded84cdd97c9d38aca4e4371921cae |
| .tls | 0 | 00000000000000000000000000000000 |
| .rdata | 512 | fa2f9fe8ee7a80aecd476e9a3151f0e2 |
| .reloc | 163328 | e2f706bb90cb1fb137cb4030f4f59dc0 |
| .rsrc | 5338112 | d6f4392aa0b1510b104d6d0860258f4d |
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:
