GtcKmdfBs.sys
Getac System Service Provider file version info
Driver on Windows LOLDrivers vulnerable driver 1 Sigma rule names it
A known vulnerable driver
5 known samples
21, 2, 0, 4 · its entry
0abca92512fc98fe6c2e7d0a33935686fc3acbd0a4c68b51f4a70ece828c066421, 2, 0, 3 · its entry
4b465faf013929edf2f605c8cd1ac7a278ddc9a536c4c34096965e6852cbfb5121, 2, 0, 3 · its entry
edbb23e74562e98b849e5d0eefde3af056ec6e272802a04b61bebd12395754e521, 2, 0, 1 · its entry
e6023b8fd2ce4ad2f3005a53aa160772e43fe58da8e467bd05ab71f3335fb82220, 2, 0, 3 · its entry
e6d1ee0455068b74cf537388c874acb335382876aa9d74586efb05d6cc362ae5From 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 GtcKmdfBs.sys?
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 GtcKmdfBs.sys in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.