So I have bought a lot of crypters here and a lot of rats. I'm sick of this shit always being detected. Like what in the actual fuck. I spent 6 HOURS making sure that shit was fucking golden. No detections what so ever. Wake up the next morning to start getting some targets, what do you know, all my fucking hard work for nothing because now it has 4 scantime detections and even windows defender picks it up on runtime. I've lost all my hard work (can't really disclose what I'm targeting, but its hard as all fuck), and it's all because of fucking detections and heuristics. What in the fuck can I do to avoid this shit? Please anyone help me, anyone.
Scantime / Runtime FUD Crypter |
(Apr 6, 2020 08:20 PM)Longdog Wrote: Probably gonna hang myself. Making scantime fud is so easy man. Like, incredibly easy. Runtime is the only thing that’s difficult.
Apr 6, 2020 08:25 PM
(This post was last modified: Apr 21, 2020 02:39 AM by The Grand Oracle.)
(Apr 6, 2020 06:56 PM)Redrum Wrote: The only true way to be code your own crypter/packer or buy a private one the public "FUD" ones are a joke. 😎 Private crypters are being sold for $1500 if they are truly have a good runtime. (Apr 6, 2020 08:25 PM)Charger Wrote: Making scantime fud is so easy man. Like, incredibly easy. Tell that to HF crypters... smh... if this shit would just be good. (Apr 6, 2020 08:29 PM)Longdog Wrote: Tell that to HF crypters... smh... if this Clay Davis would just be good. Have you tried Cyber Seal or Data Protector? (Apr 6, 2020 08:29 PM)Longdog Wrote: Tell that to HF crypters... smh... if this Clay Davis would just be good. Just make your own. All you’re doing is converting the bytes of the file to a variable and encrypting it so it’s not plain. You can use a well known algorithm such as RC4 or even just base64encode it X times. If you just increase the number of times you base64 it, it’ll change enough of your stub that AVs won’t have a full signature of your stub. Food for thought.
Apr 6, 2020 11:11 PM
(This post was last modified: Apr 6, 2020 11:11 PM by Longdog.)
(Apr 6, 2020 08:32 PM)IceY - Owned Wrote: Have you tried Cyber Seal or Data Protector? Yes, data protector was good for 6 hours until it got ran thru by the mass spreaders. (Apr 6, 2020 08:33 PM)Charger Wrote: Just make your own. All you’re doing is converting the bytes of the file to a variable and encrypting it so it’s not plain. You can use a well known algorithm such as RC4 or even just base64encode it X times. If you just increase the number of times you base64 it, it’ll change enough of your stub that AVs won’t have a full signature of your stub. I will mention this to my developers of the project. (Apr 6, 2020 08:33 PM)Charger Wrote: Just make your own. All you’re doing is converting the bytes of the file to a variable and encrypting it so it’s not plain. You can use a well known algorithm such as RC4 or even just base64encode it X times. If you just increase the number of times you base64 it, it’ll change enough of your stub that AVs won’t have a full signature of your stub. dud this is really old techniques and old algorithms. if you use those then you cant even get 100% scantime FUD. Website: nomorehome.work (Apr 7, 2020 12:56 AM)VisualSoft Wrote: dud this is really old techniques and old algorithms. Works perfectly fine for me
Apr 7, 2020 06:38 AM
(This post was last modified: Apr 7, 2020 06:49 AM by NYANxCAT.)
You are using a shared stub. it will only be fud for 4-7hours max.
You need to spend $$$$ to buy a private stub. |
|
|





![[Image: 6xBycLk.gif]](https://i.imgur.com/6xBycLk.gif)