LHA.sys
LHA 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/1c7631f0-f92f-4be5-8ba7-3eefb0601d45/
https://www.loldrivers.io/drivers/eb07ef7e-0402-48eb-8e06-8fb76eda5b84/
https://www.loldrivers.io/drivers/eb07ef7e-0402-48eb-8e06-8fb76eda5b84/
2 known samples
6.1.7600.16385 built by: WinDDK · its entry
23ba19352b1e71a965260bf4d5120f0200709ee8657ed381043bec9a938a1ade6.1.7600.16385 built by: WinDDK · its entry
e75714f8e0ff45605f6fc7689a1a89c7dcd34aab66c6131c63fefaca584539cfFrom 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 LHA.sys?
ProductMicrosoft® Windows® Operating System, LG Electronics Inc.
DescriptionLHA
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 LHA.sys in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.