Mar 18, 2012 11:59 AM
(This post was last modified: Mar 18, 2012 05:41 PM by Nichole.)
I posted this in the wrong section, and moved it.
|
.NET
Thread moved. |
 
Mar 18, 2012 12:19 PM
(This post was last modified: Mar 18, 2012 09:30 PM by Nichole.)
(Mar 18, 2012 12:09 PM)JellyFishy Wrote: Ahh okay. I'll observe it and add it to my crypter if you will allow me ofc. Not going to release the source. Just the builder. Here is a beta test if you want to quickly run. It's not infected with anything, just the crypter and a text encryptor as a dumby process. Pretty much, you'll run the TestCrypt.exe, the file encrypter will appear, and if you end the TestCrypt.exe process. The file encryptor will stil be running, with no visible process attached to it. But since the console is visible, you can just close it from the screen. The point of course is that, if the application was hidden in the background, you wouldn't be able to get rid of it. http://www.mediafire.com/?w77donutt43x9da It's harmless since the target process is only a text encrypter. If you want to stay on the safe side, just run it in sandbox or a virtual machine. (Mar 18, 2012 12:14 PM)ubbelol Wrote: Wrong section? It's not a code or anything, it's not really related to .NET and if it's true what you said about hooking ZwOpenProcess then it's not coded in .NET either. Oh sorry, it is the wrong section. Didn't mean vb. And You actually can hook ZwOpenProcess through .Net. By dynamically loading the libraries. |
|
|
