Nice
Almost all the features you mentioned depend on the dlls that the antivirus inject on the process to execute such features, and this method cleans the process from such dlls. I am not saying it will work with all antiviruses but it will work with many of them, and we have other techniques that the antivirus use such as ETW, and there are many other bypassing techniques that I haven't mentioned in the tutorial like parent process id spoofing and many morethanks for the share , i have question as , new EDR are having more capablity than static detection , for example , behavoir threat protection , local analysis , sandbox analysis , process injection , identity analytics , how can this bypass all the EDR features , will this work in the dynamic play for EDR ?
u planning to release further tutorial ? if yes , that would be greatAlmost all the features you mentioned depend on the dlls that the antivirus inject on the process to execute such features, and this method cleans the process from such dlls. I am not saying it will work with all antiviruses but it will work with many of them, and we have other techniques that the antivirus use such as ETW, and there are many other bypassing techniques that I haven't mentioned in the tutorial like parent process id spoofing and many more
Of course, I am planning to make further more private bypassing techniques. I'm sure you'll like themu planning to release further tutorial ? if yes , that would be great
damn , <3 i;m waitingOf course, I am planning to make further more private bypassing techniques. I'm sure you'll like them
Как раз что то похожее реализовано в BumbleBeeI don't really need to try it, the unhooking is an old method where all the downsides are known for a long time. I'm not saying that it doesn't work, I'm saying why it is not the best thing to do in practice.
This concrete implementation is not the best either. In general case it would be better to find and replace only hooked bytes, in that case you can restore original bytes atomically (instead of memcpy them), so there should be no race conditions. Also I really hate to see people not checking the success of winapi calls, the funny thing about that concrete code in case windows is installed on D drive for example the process will just fail with access violation exception.
elis531989.medium.com
I'm glad you like them, I will post the rest parts as soon as possible once I have time and they will contain advanced evasion techniquesSpyBoy, please 2 part. I am looking forward to))) Your 2 articles are the best. Thank you so much!!!

First of all, as mentioned in the title "part 1" and I provided only one technique, and focused on static detect and I said in the tutorial that there are plenty of techniques.what about kernel callback ? did you hear about EtwTi ?
bypass all antiviruses/EDRs Like
RockStarschoolboy...








What did you talk about? You behave like a clown. Please tell us how you bypass the Microsoft-Windows-Threat-Intelligence provider supplier from the user mode? Each of your step that you described createfilea, createfilemapping, MapViewOffile, VirtualProtect ... etc ... will be logging in every consumer which subscride on this provider, and this chain of behavor it is 100% detect as malicious every fucking silly edr and WD as is.. you don't evasion anything like thisFirst of all, as mentioned in the title "part 1" and I provided only one technique, and focused on static detect and I said in the tutorial that there are plenty of techniques.
Secondly, kernel callback and ETWTI, That's it ?? really ??
Dude you have to know something, when you want to brag or show off, you MUST do it with something incredible.
Actually, I had enough of ignorance people, that's really disgusting
Anyway, don't forget the piece of advice that I've given you![]()
слишком ахуевший ?bypass all antiviruses/EDRs Like RockStar, create your own clean undetectable...
Why do you insist that the technique that I mentioned in this post should bypass ETWTI?What did you talk about? You behave like a clown. Please tell us how you bypass the Microsoft-Windows-Threat-Intelligence provider supplier from the user mode? Each of your step that you described createfilea, createfilemapping, MapViewOffile, VirtualProtect ... etc ... will be logging in every consumer which subscride on this provider, and this chain of behavor it is 100% detect as malicious every fucking silly edr and WD as is.. you don't evasion anything like this
Of course not, your ignorance what pisses you off. Dude I can sell some techniques for you, so can understand how to bypass ETWTI without accessing the kerneltoo pissed off?
Very interesting, share your knowledge with us in part II, if you really can do it...Why do you insist that the technique that I mentioned in this post should bypass ETWTI?
I can blind your ETWTI for good and run all kind of malwares without even trying to unhook or bypass edr or anything else.
I swear I can do more than that.Very interesting, share your knowledge with us if you really can do it