That text is a combination of words from several languages. E.g.,
- Overlgen [Danish] supervise
- Vitiates [English] destroys/impairs the quality/effectiveness of
- Gennemlysningerne [Danish] the transparancy
- foliose [English] having a lobed leaf-like structure (regarding lichen)
- Uigennemtrngelige [Danish] Impenetrable
- Udgivelsesselskaber [Danish] Publishing companies
That sort of word salad is often used to avoid detection by spam/virus filters. Throw enough neutral/good words into a file and the overall "badness" score drops enough to pass, or at least to neutralize some other content that might arouse suspicion.
I'd be starting by looking for files that have the string "$platineering" or "realisticize" in them. They might not be PowerShell files (*.ps1, *.psm1, *.psd1, *.ps1xml, *.pssc, *,cdxml, *.psrc), start with those. They may also be executable files, or other script files that can interact with .Net to build PowerShell code or modules and then use that generated code from within the script. But even all of that may be futile if the code is encrypted, even with something as simple as ROT13 of Base64.
I've seen stuff that's also disguised as drivers. Check the devices (hidden ones, too) in Device Manager, and look for directories amongst the other drivers that might not match the expected names. E.g., if you have devices whose drivers are in directory "X", look for directories named "X<something else>".
You say you've use other AV. Was MalwareBytes one to those? It's pretty good (not infallible) at finding "stuff".