capt-meelo / beaconator Goto Github PK

null value error at beaconator.cna:243

Tried with x86 and x64 using PEZor. With and without Syscalls in case that made any difference.

Line 243 reads:

closef($process);

When I try to create a payload using beaconater i get the folllowing error: null value error at beaconator.cna:140

I can then copy paste the whole command from the script console to the terminal and that works properly.
I already installed pezor and updated the PATH variable.
Once I manually created the subfolder output and hard coded the full path to pezor, It is now creating the shellcode.bin file in the output folder but not creating the final payload even though it says Success beacon can be found at path/to/cna/output

If I create a payload with an option like -unhook and -x64. It will correctly create the payload. However if I then create a payload with just -x64 and -sgn, the script console says Executing: PEzor.sh -64 -unhook -sgn -shellcode -format=exe.
It is keeping the old option of -unhook when not selected(the only option I have seen that does not persist to the next generation attempt is -32). I have to reload the script after every payload generation in order to get the correct options again.

The shellcode is being correctly generated but not the binary/dll in the directoty ../output/pezor/shellcode.bin.

[*] Executing: PEzor -64 -unhook -antidebug -shellcode -format=dll /opt/tools/Beaconator/output/pezor/shellcode.bin[18:17:32] null value error at beaconator.cna:248

FYI : The command is working fine when I run it manually in a terminal.

The issue is not fixed by creating the folder output. See below:

Executing: PEzor.sh -64 -unhook -antidebug -shellcode -format=exe /home/simon.davies/Cobalt_Strike_Aggressor_Scripts/Beaconator/output/shellcode.bin[10:31:56] null value error at beaconator.cna:140