bs_rcio64.sys

I/O Interface driver file file version info

Driver on Windows LOLDrivers vulnerable driver 1 Sigma rule names it

A known vulnerable driver

from LOLDrivers

T1068Exploitation for Privilege Escalation

Its entrieshttps://www.loldrivers.io/drivers/cacf18a5-6d7d-4a63-92d4-bda386a3da18/
https://www.loldrivers.io/drivers/e7c958da-fd5d-40d6-975e-582c6fee7f69/

2 known samples

10.0.1901.1100 · its entry

d205286bffdf09bc033c09e95c519c1c267b40c2ee8bab703c6a2d86741ccd3e

its entry

73327429c505d8c5fd690a8ec019ed4fd5a726b607cabe71509111c7bfe9fc7e

From LOLDrivers (Apache 2.0). A driver is known by its hash: a sample under another name is the same driver. In Ceplin, "<sha256>".whatis() says which sample a hash is.

Is it the real bs_rcio64.sys?

file version info and known copies

ProductBIOSTAR I/O driver, BIOSTAR Group

DescriptionI/O Interface driver file

From the file’s version info, as recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look.

What detects it

Sigma

Sigma names bs_rcio64.sys in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.