RapidFireServer64.dll threat report
ThreatInfo file report
RapidFireServer64.dll
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as PUP.DriverMax. 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.DriverMax
- Recommended action
- Scan and remove
- Last analysis
- 2022-02-17 23:04:15 (4 years ago)
- File hash
- 33aafc946ff447d710846ab1199cbc33
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as PUP.DriverMax.
First seen 2022-02-17 23:04:15 (4 years ago); latest analysis 2022-02-17 23:04:15 (4 years ago).
Company metadata: Advanced Micro Devices, Inc.. Product metadata: AMD Rapid Fire.
Signed by Advanced Micro Devices, Inc.;Advanced Micro Devices INC.;Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Compare the MD5 above with the file found on the device.
- Check whether the file appears in the observed locations or under one of the alternate names.
- Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.
File context
RapidFireServer64.dll is a Windows file recorded in the ThreatInfo database. It is associated with AMD Rapid Fire. The reported company name is Advanced Micro Devices, Inc.. The current detection status is PUP.DriverMax, based on the latest analysis from 2022-02-17 23:04:15 (4 years ago).
If RapidFireServer64.dll 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.DriverMax.
File Details
| Product Name: | AMD Rapid Fire |
| Company Name: | Advanced Micro Devices, Inc. |
| MD5: | 33aafc946ff447d710846ab1199cbc33 |
| Size: | 45 KB |
| First Published: | 2022-02-17 23:04:15 (4 years ago) |
| Latest Published: | 2022-02-17 23:04:15 (4 years ago) |
| Status: | PUP.DriverMax (on last analysis) | |
| Analysis Date: | 2022-02-17 23:04:15 (4 years ago) |
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.
Overview
| Signed By: | Advanced Micro Devices, Inc.;Advanced Micro Devices INC.;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on RapidFireServer64.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %localappdata%\innovative solutions\drivermax\agent\restore\l22oh87fbx1xy1595jol30yaa800a11l48a2cqvju3551257u3\display\pci_ven_1002&dev_9874&rev_e2 |
ThreatInfo has observed RapidFireServer64.dll 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:
| 100.0% |
The strongest geographic signal for this file is Argentina with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
| Windows 10 | 100.0% |
The most common operating system signal for RapidFireServer64.dll is Windows 10 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
RapidFireServer64.dll is identified as pe for 64 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: | 64 |
| Image Base: | 0x0000000180000000 |
| Entry Address: | 0x00002700 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 9216 | 07366d143fd95230fb204c5eb865adb2 |
| .rdata | 5632 | 96d8061f3f77b8713c28bc97746cde71 |
| .data | 512 | e6fa46abd95c3afde7b3e9aea537c12f |
| .pdata | 1024 | 6c72d381b66fcfc87360b0d3e72d9341 |
| .tls | 512 | 1f354d76203061bfdd5a53dae48d5435 |
| .gfids | 512 | e3f33c75899e6a18ab3152e3490c664b |
| .rsrc | 1536 | 27a0f79e3d33cf494aa483ba001ca25b |
| .reloc | 512 | 590f2e320aafee2d3e2181e7aa7b2ef0 |
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:
