GridinSoft Threat Intelligence

$RDB814T.exe file report

Clean record File reputation report
MD5 5a7e807514a8576fae63d87434bc7044
Latest seen 2021-02-19 16:54:52 (5 years ago)
First seen 2020-04-22 03:01:44 (6 years ago)
Size 62 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-04-22 03:01:44 (6 years ago); latest analysis 2021-02-19 16:54:52 (5 years ago).

Digital signature

Signed by Beijing Kingsoft Security software Co.,Ltd. ThreatInfo marks this publisher as trusted for this record.

Observed locations

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

  1. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

$RDB814T.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-02-19 16:54:52 (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.

MD5: 5a7e807514a8576fae63d87434bc7044
Size: 62 MB
First Published: 2020-04-22 03:01:44 (6 years ago)
Latest Published: 2021-02-19 16:54:52 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-19 16:54:52 (5 years ago)
Signed By: Beijing Kingsoft Security software Co.,Ltd
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.

%sysdrive%\$recycle.bin
%temp%\onlineinstall

ThreatInfo has observed $RDB814T.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.

Windows 10 75.0%
Windows 7 25.0%

The most common operating system signal for $RDB814T.exe is Windows 10 with 75.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.

$RDB814T.exe is identified as pe for 32-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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x000f770b
Image base 0x00400000

PE Sections:

Sections 7
Raw data 2041422

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 1266688 bytes · 62.0% of section data
MD5 c9aa491e65ebe81e6f890be59e7575e9
.rdata 297472 bytes · 14.6% of section data
MD5 ae87533950c9401c9e8d3eb8ec5012a6
.data 176128 bytes · 8.6% of section data
MD5 999df108f59f8675526c75a833c94fe0
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 238080 bytes · 11.7% of section data
MD5 fc17e14a3a09844acbe03a05457fcadc
.reloc 62464 bytes · 3.1% of section data
MD5 a10daab995ac6e5dba8178db49dcb7c4
.rdata2 78 bytes · 0.0% of section data
Uncommon name
MD5 d70b674e4ca542c93d5befd28d47f422

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.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 5a7e807514a8576fae63d87434bc7044.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.