Dec 23, 2016 07:48 PM (This post was last modified: Dec 28, 2016 11:41 AM by DiarrheaProliv.)
[align=center]Here is a REAL REVIEW about RataProtector crypter...
This crypter not working at all, also Rata protector is NOT FUD!!! ESET NOD 32 catch it as Trojan.MSIL/Kryptic HYJ - a variant of MSIL/Injector.QYD
It has been detected almost by all major av!
Be careful, the owner and his freinds post FAKE SCANS and FAKE VOUCHES in official thread!
1. You are enabling all of those disablers and you expect it to be runtime FUD?
2. Those are gen detections.
3. Do you even have any idea what you are doing?
Here is a REAL REVIEW about RataProtector crypter...
This crypter not working at all, also Rata protector is NOT FUD!!! ESET NOD 32 catch it as Trojan.MSIL/Kryptic HYJ - a variant of MSIL/Injector.QYD
It has been detected almost by all major av!
Be careful, the owner and his freinds post FAKE SCANS and FAKE VOUCHES in official thread!
Here is VIDEO PROOF
Try changing icon and assembly. Also only enable what you really need in the crypter.
Dec 23, 2016 08:24 PM (This post was last modified: Dec 23, 2016 08:47 PM by DiarrheaProliv.)
(Dec 23, 2016 08:14 PM)SIM-2053312 Wrote: Try changing icon and assembly. Also only enable what you really need in the crypter.
Tired, but again NOT FUD. 🤨
(Dec 23, 2016 08:09 PM)Codefuser Wrote: 1. You are enabling all of those disablers and you expect it to be runtime FUD?
2. Those are gen detections.
3. Do you even have any idea what you are doing?
1. If Crypter is good then it will be FUD!
2. NO! MSIL.Injector and Kryptic is NOT Generic!
3. Yes of course
OP those are called false detections they're not caused by the crypter, but your current assembly and Icon. If you'd like I can help you get a FUD stub.
I only saw ESET, that is normal from a public crypter.
All others detections are not from the crypter but from the icon / assembly, just change it and you'll get 1 / 35.
You can't have 0 detection with a public crypter, you just can't.
Dec 23, 2016 11:21 PM (This post was last modified: Dec 23, 2016 11:32 PM by Twistd.)
OP you're like a fucking disease to this forum. Please just fuck off and leave with your 5 multis.
(Dec 23, 2016 10:07 PM)Glyco Wrote: OP those are called false detections they're not caused by the crypter, but your current assembly and Icon. If you'd like I can help you get a FUD stub.
Dead wrong! Of course it's not a false positive? How can you even call it a false positive? I'm amazed. Of course they are created by the crypter, it's a generic behavior (heuristic) detection. Change the codeflow or resources a little and it will be good to go. Just stop being a jackass giving it false positive name.
(Dec 23, 2016 11:21 PM)Twistd Wrote: OP you're like a fucking disease to this forum. Please just fuck off and leave with your 5 multis.
Dead wrong! Of course it's not a false positive? How can you even call it a false positive? I'm amazed. Of course they are created by the crypter, it's a generic behavior (heuristic) detection. Change the codeflow or resources a little and it will be good to go. Just stop being a jackass giving it false positive name.
I am pretty sure half of those detection can be removed with a HQ icon and assembly.
(Dec 24, 2016 12:00 AM)Codefuser Wrote: Doesn't mean it is not a code detection.
Well obviously no one is denying is denying its a code detection or not, I am just pointing out the obvious that it pertinently has a little bit to do with the icon and assembly.