GridinSoft Threat Intelligence
RTCOM64.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2018-07-13 10:13:53 (7 years ago); latest analysis 2021-01-02 12:33:00 (5 years ago).
Company metadata: Realtek Semiconductor Corp.. Product metadata: RTCOMDLL Module.
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
RTCOM64.dll is a Windows file recorded in the ThreatInfo database. It is associated with RTCOMDLL Module. The reported company name is Realtek Semiconductor Corp.. The current detection status is Clean, based on the latest analysis from 2021-01-02 12:33:00 (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: | RTCOMDLL Module |
| Company Name: | Realtek Semiconductor Corp. |
| MD5: | 1c64d5ace5695fd1a52b8d0b938de243 |
| Size: | 1 MB |
| First Published: | 2018-07-13 10:13:53 (7 years ago) |
| Latest Published: | 2021-01-02 12:33:00 (5 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2021-01-02 12:33:00 (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:
| %localappdata%\innovative solutions\drivermax\agent\uploads\813p8pv216gto3970i886r0t4o2g62kft83dlng0fn94200t28\media |
| %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 RTCOM64.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 RTCOM64.dll across 4 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 50.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 RTCOM64.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
RTCOM64.dll is identified as pe for 64-bit 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 Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
ce925173061cf702104632f08a91511a
e8544e866fdb3a904b7430ee96787e77
801399122b4b8330d3ca09ea80b47996
e6939e471802a9ba8bf912a8e9656e45
cb3486816a5d61555287f9594756f9f8
84ccaa8494da309c2bdb5ee5054f26a3
1b6c9d6af8cffcfae35f01ef08116503
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.