Hey all,
So myself and I am sure many others have had compatibility issues with DPV2 and PPLV11 files being crypted...So I thought I'd make a quick and simple tutorial on how to crypt your file while it is compatible with the crypter...
1. Make your logger
This is simple, do your logger how you would usually do it, though to ensure the highest compatibility and undetectability, use my settings:
![[Image: q3oNzpx.png]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_thYg1XNLz2ZnMaqTqlizKWjMqcbYsAwonwJunSdAOmtpvqZk7T2MO0fuSJddwc83DA36_CiDI8oFlvur2obbPh2w=s0-d)
This has the lowest detection rate and least suspicion to AV's. Disabling Stealer Logs is EVEN LESS suspicious and could possibly stay FUD for a while, though they are the main reason why I use the tool so I leave it on.
2. Crypt your file - Step 1
Step 1 is to put your file into Data Protector V2, and make sure it is injecting/executing as ITSELF... not AppLaunch or vbc...these will not work and make your file crash!!![[Image: 8a7KNx3.png]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_uIbj0F-CD28SUNZ1QinRFmu-eLriPD7VlAV50fEA5OvbWGEz107mpTXOyPYANufwdpNLG6P7SswnJvNINN6SKQXg=s0-d)
3. Crypt your file - Step 2
Next is to adjust the settings. Melt, Add to startup and fake error SHOULD NOT be enabled...why?
Melt - You already have this enabled on your crypter, doing it again can prolong runtime and also crash your logger. It is not recommended to melt twice
Add to startup - Double startup registry's can confuse your logger and cause a crash
Fake error - Two fake errors will look extremely suspicious on the user end!! Though if that's what your into, go for it. This may also crash your file, I've never tested it.
Again, For lowest detection rates, you do not need to bind files, create downloaders or change creation dates...therefor I crossed these out. If you want to, you are more than welcome to try these options out, though I do not recommend it unless you absolutely have to.
I used Pump File, just to make it look a little more legit in size.
![[Image: zn0ZjDJ.png]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_tp1TWd4wHYMG-jhvq93S3bVc7VjTXjVashCwbeOS1KzsFzjcFGJxwKcsurpDr8BJkZc4Mc-wGO3ND1-frpH7Iw=s0-d)
4. Scanning your file - Step 3
number one rule, NEVER use an external scanner...ALWAYS use the one from Data Protector, the one that is internal! If you scan on sites like virus total, your file will be 10/46 in no time, and it'll definitely hurt the crypter.
Now, choose your file and scan to see if it is FUD!
![[Image: CUTPcTx.png]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_vlSaQLW8qHx8orfXLyxKl8EAoY-bep_lQJ9bfM4o465330H_iy3y0CZxBxdXmB4Qn3erWdLzhhGqOzKlFS0ariDg=s0-d)
5. As you can see, my file is FUD!
![[Image: T4CBCR9.png]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_vCJ6CeknJHURHqgsw87X4FnrqToFahb3xZedVpLk3mEh9U6lY5YcsIy7hpUbKbKuubkLfn6KoF8Z0jD4vsUGNh=s0-d)
6. Upload your file - Step 4
Now it's the easy part...uploading! Find a good host like zippyshare.com.
This is where you can upload your files!
7. Enjoy!
Start spreading and infecting your victims with a FUD logger by Data Protector V2 and Predator Pain V11!
Thanks for reading! Feedback is appreciated :D
So myself and I am sure many others have had compatibility issues with DPV2 and PPLV11 files being crypted...So I thought I'd make a quick and simple tutorial on how to crypt your file while it is compatible with the crypter...
1. Make your logger
This is simple, do your logger how you would usually do it, though to ensure the highest compatibility and undetectability, use my settings:
This has the lowest detection rate and least suspicion to AV's. Disabling Stealer Logs is EVEN LESS suspicious and could possibly stay FUD for a while, though they are the main reason why I use the tool so I leave it on.
2. Crypt your file - Step 1
Step 1 is to put your file into Data Protector V2, and make sure it is injecting/executing as ITSELF... not AppLaunch or vbc...these will not work and make your file crash!!
3. Crypt your file - Step 2
Next is to adjust the settings. Melt, Add to startup and fake error SHOULD NOT be enabled...why?
Melt - You already have this enabled on your crypter, doing it again can prolong runtime and also crash your logger. It is not recommended to melt twice
Add to startup - Double startup registry's can confuse your logger and cause a crash
Fake error - Two fake errors will look extremely suspicious on the user end!! Though if that's what your into, go for it. This may also crash your file, I've never tested it.
Again, For lowest detection rates, you do not need to bind files, create downloaders or change creation dates...therefor I crossed these out. If you want to, you are more than welcome to try these options out, though I do not recommend it unless you absolutely have to.
I used Pump File, just to make it look a little more legit in size.
4. Scanning your file - Step 3
number one rule, NEVER use an external scanner...ALWAYS use the one from Data Protector, the one that is internal! If you scan on sites like virus total, your file will be 10/46 in no time, and it'll definitely hurt the crypter.
Now, choose your file and scan to see if it is FUD!
5. As you can see, my file is FUD!
6. Upload your file - Step 4
Now it's the easy part...uploading! Find a good host like zippyshare.com.
This is where you can upload your files!
7. Enjoy!
Start spreading and infecting your victims with a FUD logger by Data Protector V2 and Predator Pain V11!
Thanks for reading! Feedback is appreciated :D
Thanks for reading my news about [TUTORIAL] How to use Data Protector V2 FUD Crypter with Predator Pain Logger V11+ at my blog Tic Droid if you want too share this article, please put the resource, and if you think this article is very usefully dont forget to bookmark this site with CTRL + D on your keyboard to web browser.