rtport.sys
Generic Port I/O for Win32 file version info
Driver on Windows LOLDrivers vulnerable driver 1 Sigma rule names it
A known vulnerable driver
8 known samples
5.0.2195.1711 · its entry
3c0a36990f7eef89b2d5f454b6452b6df1304609903f31f475502e4050241dd85.0.2195.1711 · its entry
71423a66165782efb4db7be6ce48ddb463d9f65fd0f266d333a6558791d158e55.0.2195.1711 · its entry
8fe429c46fedbab8f06e5396056adabbb84a31efef7f9523eb745fc60144db655.00.2195.1620 · its entry
6f806a9de79ac2886613c20758546f7e9597db5a20744f7dd82d310b7d6457d05.00.2195.1 · its entry
a29093d4d708185ba8be35709113fb42e402bbfbf2960d3e00fd7c759ef0b94e5.00.2195.1 · its entry
c490d6c0844f59fdb4aa850a06e283fbf5e5b6ac20ff42ead03d549d8ae1c01b5.00.2195.1 · its entry
e3dbafce5ad2bf17446d0f853aeedf58cc25aa1080ab97e22375a1022d6acb161.0.01.0000 · its entry
ff322cd0cc30976f9dbdb7a3681529aeab0de7b7f5c5763362b02c15da9657a1From 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 rtport.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 rtport.sys in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.