GridinSoft Threat Intelligence
RtsPer.sys file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2018-04-22 17:08:56 (8 years ago); latest analysis 2024-01-30 23:55:56 (2 years ago).
Company metadata: Realsil Semiconductor Corporation. Product metadata: Windows (R) Win 7 DDK driver.
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
RtsPer.sys is a Windows file recorded in the ThreatInfo database. It is associated with Windows (R) Win 7 DDK driver. The reported company name is Realsil Semiconductor Corporation. The current detection status is Clean, based on the latest analysis from 2024-01-30 23:55:56 (2 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: | Windows (R) Win 7 DDK driver |
| Company Name: | Realsil Semiconductor Corporation |
| MD5: | 780b2ee5577ae598eb4b7a2f4fc0d986 |
| Size: | 844 KB |
| First Published: | 2018-04-22 17:08:56 (8 years ago) |
| Latest Published: | 2024-01-30 23:55:56 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-01-30 23:55:56 (2 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:
| %appdata%\uniblue\driverscanner\drivers\155147\0007-rtsxstor_10.0.370.188\rtsxstor_10.0.370.188 |
| %appdata%\driverfinder\download\436149\0007-rtsxstor_10.0.370.188\rtsxstor_10.0.370.188 |
| %localappdata%\slimware utilities inc\driverupdate\backups\20181223t082738657\pci |
| %localappdata%\slimware utilities inc\driverupdate\backups\20180921t210014128\pci |
| %localappdata%\slimware utilities inc\driverupdate\backups\20180921t210827748\pci |
ThreatInfo has observed RtsPer.sys 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 RtsPer.sys across 5 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 37.5% 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 RtsPer.sys is Windows 10 with 62.5% 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
RtsPer.sys is identified as pe for 64-bit systems. The subsystem is Native. 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.
ccfb6ae371cbd338adb58ad4090a3518
8fc149be0a6de474fb11e1be4412fc34
51b7ca5cae0ac47a3c7b2c38a7f0e28f
00309afd906d4492ad6ea303d296287d
1cf2856b26691be80e10679aee1138e4
935c7fec26dd035737a512598a69138d
e4312d26d49e647716a2c344bbf3fb9b
0f0ea758e5c29283f9d7c07c074b0ce3
9bacc5aafab7948f131a123c9c7e5478
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.