2.sys
Driver on Windows LOLDrivers malicious 1 Sigma rule names it
A known malicious driver
T1068Exploitation for Privilege Escalation
Its entrieshttps://www.loldrivers.io/drivers/0c0198a3-5c63-4a9b-abe9-88a810602329/
https://www.loldrivers.io/drivers/bb1f80f3-d2fd-463e-9403-57c919bd976b/
https://www.loldrivers.io/drivers/bb1f80f3-d2fd-463e-9403-57c919bd976b/
2 known samples
88076e98d45ed3adf0c5355411fe8ca793eb7cec1a1c61f5e1ec337eae267463df72cb33a23ae8f6f9dc64bb738fcfaea959368ce05cf399f3c7db5e90104bd7From 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.
What detects it
Sigma names 2.sys in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.