superbmc.sys
superbmc file version info
Driver on Windows LOLDrivers vulnerable driver 1 Sigma rule names it
A known vulnerable driver
T1068Exploitation for Privilege Escalation
6 known samples
2.0.0.0 · its entry
f8430bdc6fd01f42217d66d87a3ef6f66cb2700ebb39c4f25c8b851858cc4b351d804efc9a1a012e1f68288c0a2833b13d00eecd4a6e93258ba100aa07e3406f1deae340bf619319adce00701de887f7434deab4d5547a1742aeedb5634d23c6326b53365f8486c78608139cac84619eff90be361f7ade9db70f9867dd94dcc9a6f8aa3de5b4aea58eddd45807d722c864d4bc4a38ad573174af864e21f0d526c9c60f560440ff16ad3c767ff5b7658d5bda61ea1166efe9b7f450447557136eFrom 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 superbmc.sys?
Productsuperbmc, Super Micro Computer, Inc.
Descriptionsuperbmc
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 superbmc.sys in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.