Information about WR64.sys

WR64.sys

WR64.sys is a Windows file recorded in the ThreatInfo database. It is associated with WinRing0. The reported company name is OpenLibSys.org. The current detection status is Undefined, based on the latest analysis from 2025-01-29 23:02:43 (a year ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: WinRing0
Company Name: OpenLibSys.org
MD5: d974b8d7090d75ef71fc5b3738857972
Size: 14 KB
First Published: 2022-04-18 23:15:16 (4 years ago)
Latest Published: 2025-01-29 23:02:43 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-01-29 23:02:43 (a year ago)
Signed By: Noriyuki MIYAZAKI
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on WR64.sys is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.

%appdata%\windows
%appdata%\windows
%appdata%\windows
%appdata%\windows
%appdata%\windows

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

20.0%
20.0%
20.0%
20.0%
20.0%

The strongest geographic signal for this file is United States with 20.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for WR64.sys 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.

WR64.sys is identified as pe for 64 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.

Subsystem: Native
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000000010000
Entry Address: 0x00005008

PE Sections:

Name Size of data MD5
.text 2048 1c3d5bb2285dafcf3b7746bf717c1a51
.rdata 512 08362d1269d5a5ef4e7560cab993590d
.data 512 043c46095689123e1f5be96c109c2f46
.pdata 512 077af14197899077aa36d2c72ba1773f
INIT 1024 ba375d2de342e7d7a93487a35ea5d36d
.rsrc 1024 5459c1fdb222b651d36692c4ca5df895

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: