Skip to content

Commit 6cfd38a

Browse files
authoredJun 18, 2021
Update README.md
adding -a option
1 parent 01c5208 commit 6cfd38a

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed
 

‎README.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -6,21 +6,22 @@ Have these local admin credentials but the EDR is standing in the way? Unhooking
66
#### What can it do?
77
```
88
Usage: backstab.exe <-n name || -p PID> [options]
9-
-n, Choose process by name, including the .exe suffix
9+
-n, Choose process by name, including the .exe suffix
1010
-p, Choose process by PID
1111
-l, List handles of protected process
1212
-k, Kill the protected process by closing its handles
1313
-x, Close a specific handle
1414
-d, Specify path to where ProcExp will be extracted
1515
-s, Specify service name registry key
1616
-u, Unload ProcExp driver
17+
-a, adds SeDebugPrivilege
1718
-h, Print this menu
1819
1920
Examples:
2021
backstab.exe -n cyserver.exe -k [kill cyserver]
2122
backstab.exe -n cyserver.exe -x E4C [Close handle E4C of cyserver]
2223
backstab.exe -n cyserver.exe -l [list all handles of cyserver]
23-
tbackstab.exe -p 4326 -k -d c:\\driver.sys [kill protected process with PID 4326, extract ProcExp driver to C:\ drive]
24+
backstab.exe -p 4326 -k -d c:\\driver.sys [kill protected process with PID 4326, extract ProcExp driver to C:\ drive]
2425
```
2526

2627

@@ -40,7 +41,7 @@ Here is a quick rundown of what happens
4041
#### What you should also know
4142
1. The behavior of the tool mimics that of ProcExp. ProcExp drops the driver to the disk, create registry key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services, calls NtLoadDriver, and then delete the registry key
4243
2. You can specify the location to which the driver is dropped and the service name
43-
3. When done, the app will unload the driver if you specify the option to unload the driver. The driver is unloaded by first re-creating the registry keys and then calling NtUnloadDriver
44+
3. When done, the app will unload the driver. The driver is unloaded by first re-creating the registry keys and then calling NtUnloadDriver
4445
4. The loaded driver is signed by MS
4546
5. The process does not attempt to directly kill protected processes handles, it instructs ProcExp driver to kill them. You won't be accused of attempting to tamper with any processes
4647

0 commit comments

Comments
 (0)
Please sign in to comment.