BSMI.sys
SMI Driver file version info
Driver on Windows LOLDrivers vulnerable driver 1 Sigma rule names it
A known vulnerable driver
T1068Exploitation for Privilege Escalation
Its entrieshttps://www.loldrivers.io/drivers/47724cc1-bf75-4ab7-a47a-355a9aa30de1/
https://www.loldrivers.io/drivers/bf01915d-045f-442c-a74e-25c56182123f/
https://www.loldrivers.io/drivers/bf01915d-045f-442c-a74e-25c56182123f/
2 known samples
1.0.0.3 · its entry
552f70374715e70c4ade591d65177be2539ec60f751223680dfaccb9e0be0ed91.0.0.3 · its entry
59626cac380d8fe0b80a6d4c4406d62ba0683a2f0f68d50ad506ca1b1cf25347From 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 BSMI.sys?
DescriptionSMI Driver
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 names BSMI.sys in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.