The issue appears when the user tries to get a reverse back connect shell on the box and that is because of using '&' at the end of the used one liner backdoor.
@g0tmi1k used nohub and the special char '&' at the end of each payload to execute it as a background process.
The idea to send an encoded payload using some encoder e.g. base64 will force the user to customize the uploaded php shell on the victim box to decode the payload using the same encoder we use in our backend module.
so a quick dirty patch may help in getting over the issue, something like adding new line after each on-liner payload.
The issue appears when the user tries to get a reverse back connect shell on the box and that is because of using '&' at the end of the used one liner backdoor.
@g0tmi1k used nohub and the special char '&' at the end of each payload to execute it as a background process.
The idea to send an encoded payload using some encoder e.g. base64 will force the user to customize the uploaded php shell on the victim box to decode the payload using the same encoder we use in our backend module.
so a quick dirty patch may help in getting over the issue, something like adding new line after each on-liner payload.