GridinSoft Threat Intelligence
RtPgEx64.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2019-12-01 03:04:24 (6 years ago); latest analysis 2021-01-02 12:41:36 (5 years ago).
Company metadata: Realtek Semiconductor Corp.. Product metadata: Realtek LFX/GFX DSP UI component.
Signed by Realtek Semiconductor Corp.. ThreatInfo marks this publisher as trusted for this record.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
RtPgEx64.dll is a Windows file recorded in the ThreatInfo database. It is associated with Realtek LFX/GFX DSP UI component. The reported company name is Realtek Semiconductor Corp.. The current detection status is Clean, based on the latest analysis from 2021-01-02 12:41:36 (5 years ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Realtek LFX/GFX DSP UI component |
| Company Name: | Realtek Semiconductor Corp. |
| MD5: | 5dd8fae31471ae8b216eab911671bcfa |
| Size: | 3 MB |
| First Published: | 2019-12-01 03:04:24 (6 years ago) |
| Latest Published: | 2021-01-02 12:41:36 (5 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2021-01-02 12:41:36 (5 years ago) |
Overview
| Signed By: | Realtek Semiconductor Corp. |
| Status: | Trusted Publisher |
ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.
Common Places:
| %commonappdata%\reviversoft\pc reviver\s-1-5-21-2927450747-2507301955-2091121292-1001\driver updater\downloads\2c1ae552-2137-4f0f-a13e-5da64ef8b93c |
| %commonappdata%\reviversoft\pc reviver\s-1-5-21-2927450747-2507301955-2091121292-1001\driver updater\downloads\53 |
| %localappdata%\innovative solutions\drivermax\agent\uploads\066d08f813a8sw17yfgt2j4t2774w18n318990ifmm951wrpf5\media |
| %localappdata%\innovative solutions\drivermax\agent\restore\u67ew66793h30uoq7y54tjhavi9wn929qx2w7284y822m2cbnq\media |
ThreatInfo has observed RtPgEx64.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.
Geographic signal
Observed country distribution
ThreatInfo has seen RtPgEx64.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Saudi Arabia with 60.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for RtPgEx64.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
RtPgEx64.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
66509cb73b9994940debe2830c685062
03091df269711285a7a461d8e634540e
99204cc04676a46cbef42e4dcfe11d80
4ddc2edcc80a05d8874789de569cf4b5
c166fff08900cb6fe5e3e94f5bc44a7d
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.
Report conclusion
This hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.