The size of the DLL is massive. I guess it would take months, if not years, of 1 FTE to analyze everything this DLL does.
But before you can start disassembling and decompiling it, you must unpack it.
Unpacking is often a problem, because the packers are designed to make unpacking for reverse engeneering hard.
If these three DLLs all come from the same source (Majestic Software), then they recently started to pack the DLL to protect it against snooping eyes.
One way to check the DLL is to unpack it, and then submit it to VT. But unfortunately, these packers have no unpacker.
If I have time, I'll have a go at it by running it in a VM and dumping it from the process memory.
SANS ISC Senior Handler
Microsoft MVP 2011-2016 Consumer Security, Windows Insider MVP 2016-2019
If you send me messages, per Bleeping Computer's Forum policy, I will not engage in a conversation, but try to answer your question in the relevant forum post. If you don't want this, don't send me messages.
Stevens' law: "As an online security discussion grows longer, the probability of a reference to BadUSB approaches 1.0"