Page 1 of 1

Looking for userland rootkits Win7 !!x64!!

PostPosted:Sat Dec 01, 2012 3:20 pm
by Microwave89
Hi there, all!

I'm a student 23 yrs old and I recently got back interested in rootkits again, when the incredibly famous TDL series begun to appear.
After trying to get a sample of them I was leaded to sysinternals.com and shortly after to kernelmode.in.
However, those are real world RKs and they are of course quite dangerous for a newbie like me, as they can do and mess up easily everything their makers even think about, so I decided to not just download a TDL4+ sample, but to make an attempt to get a userland rootkit first.
So I'm looking for some (tame) userland rootkits which basically are capable of running on a x64 machine as I own one.
That means, the MUST be able to inject their dll into a legit x64 process (I will provide admin rights, that is not a big deal) OR run as an x64 process.
It's btw not important that they don't have any payload, however I'm going to make an attempt to take that out by code redirects or so.
And if you HAD a kernel rootkit which runs on x64 too and is REALLY REALLY HARMLESS, you would be invited to let me know as well.

But why all that? I will try to take you back to WinXP x86 time.
Someone of sure might remember back in early times (2005..2007), when a demo rootkit called "vanquish" appeared.
It was based on dll injection technique and it really was extremely powerful even though it only used to run in user mode! And it was so tame, because its only intention it had was to hide itself and all of its traces througout the whole system.
I can remember so clearly: I started vanquish loader, it unpacked its dll and injected it into all processes it had access to, and like magic the loader exe was disappeared.
Then in a hacker book I was told to rename some normal files into something like uvwgug94vanquish7tgn7, and when I tried that, they also pretended to not be on the system anymore. You could mess around with tools like process explorer and taskmgr but none of them seemed to be able to show neither the rootkit process (as it was only the vanquish.dll) nor any hidden files or even registry entries (regedit). It was something outstanding spectacular in my opinion.
Then I launched IceSword, it forced its .sys into the kernel and revealed that vanquish.dll in fact existed at my hard disk and also that it has been injected into lots of legit processes.

Nowadays, both OS and platforms have changed and until now I wasn't able to see vanquish.dll working again, since it's obvious that it doesn't affect explorer.exe, if the vanquish.dll is injected into an explorer.exe *32 which has been started only for that reason -__-. Thus, no hidden files.. :( :(
If you have read until here, you might have understood why the vanquish was so awesome in my guess.
And possibly...for some reason someone even might have source code of vanquish.dll, then I will try to understand what makes it that powerful...


You know, I'm quite new to this community and I hope that my request isn't to much against the forum rules, although I maybe better asked in the malware request forum.
And of course, you might not be interested in lame ring3 RK stuff.... ;)

But give me a chance, I want to experience the amazing vanquish feeling again.


Best regards

Microwave89

Re: Looking for userland rootkits Win7 !!x64!!

PostPosted:Sun Dec 02, 2012 4:28 am
by EP_X0FF
userland rootkits Win7 !!x64!!
1. ITW not exists or not widely known. Why? - Because they are nonsense.
Someone of sure might remember back in early times (2005..2007), when a demo rootkit called "vanquish" appeared.
2. Vanquish? It was piece of crap dll injection lolkit with set of useless Win32 API lame hooks. It was lame even for 2005.

All it "wondeful" file hiding features were based on kernel32.dll lame splicing E9 hooks - FindFirstFileExW, FindNextFileW. And others:
Code: Select all
[400]winlogon.exe-->kernel32.dll-->LoadLibraryExW, Type: Inline - RelativeJump 0x7C801AF5-->01AE34CC [vanquish.dll]
[400]winlogon.exe-->kernel32.dll-->CreateProcessW, Type: Inline - RelativeJump 0x7C802336-->014131C3 [vanquish.dll]
[400]winlogon.exe-->kernel32.dll-->CreateProcessA, Type: Inline - RelativeJump 0x7C80236B-->014130C0 [vanquish.dll]
[400]winlogon.exe-->kernel32.dll-->FreeLibrary, Type: Inline - RelativeJump 0x7C80AC6E-->01413DA8 [vanquish.dll]
[400]winlogon.exe-->kernel32.dll-->FindFirstFileExW, Type: Inline - RelativeJump 0x7C80EB0D-->01413E60 [vanquish.dll]
[400]winlogon.exe-->kernel32.dll-->FindNextFileW, Type: Inline - RelativeJump 0x7C80EFCA-->01413F3C [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->RegCloseKey, Type: Inline - RelativeJump 0x77DC6C17-->01414C22 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->RegEnumKeyExW, Type: Inline - RelativeJump 0x77DC7BC9-->01414D72 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->RegEnumValueW, Type: Inline - RelativeJump 0x77DC7EDD-->01414E54 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->RegEnumKeyW, Type: Inline - RelativeJump 0x77DCD5D4-->01414C90 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->RegEnumKeyExA, Type: Inline - RelativeJump 0x77DD5196-->01414DE3 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->RegEnumKeyA, Type: Inline - RelativeJump 0x77DD5398-->01414D01 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->CreateProcessAsUserW, Type: Inline - RelativeJump 0x77DDA889-->014133C9 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->EnumServicesStatusA, Type: Inline - RelativeJump 0x77DE6B17-->014150B0 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->RegEnumValueA, Type: Inline - RelativeJump 0x77DE9B8F-->01414EC5 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->CreateProcessAsUserA, Type: Inline - RelativeJump 0x77E00C80-->014132C6 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->RegQueryMultipleValuesA, Type: Inline - RelativeJump 0x77E25667-->01414FEF [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->RegQueryMultipleValuesW, Type: Inline - RelativeJump 0x77E259C9-->01414F36 [vanquish.dll]
[400]winlogon.exe-->advapi32.dll-->EnumServicesStatusW, Type: Inline - RelativeJump 0x77E27D09-->014155D7 [vanquish.dll]
and initial vanquish.dll mapping from special service it installs.
Then I launched IceSword, it forced its .sys into the kernel and revealed that vanquish.dll in fact existed at my hard disk and also that it has been injected into lots of legit processes.
3. Lol. Using China BSOD-generator with lame ARK features against primitive user mode kernel32.dll hooker. Cool story, bro.

4. With API list posted above and this you can create the same lolkit compatible with x64. No, we do not give tips on how to create such malware or any other malware.

Thread closed.