[ Linux Machine ] Session status gets in "undefined" state after closing the terminal in victim machine where the payload was executed

[yaseerkhan]

I am not sure if it's only me or if others encountered this issue as well.

1. When I use "shell {session ID}" and run commands I observed behavior in the victim machine terminal where I pasted the payload.
2. After closing the terminal where I pasted the payload, the status of the session becomes undefined and it doesn't work anymore.

[stevenhay]

Also happening on Windows, payload runs correctly, session gets generated but then the powershell instance quits and the session sits on "Undefined" and no commands work

[yaseerkhan]

Also happening on Windows, payload runs correctly, session gets generated but then the powershell instance quits and the session sits on "Undefined" and no commands work

have you tried turning off real time protection in firewall settings?

[SolsticeSpectrum]

I am not sure if it's only me or if others encountered this issue as well.

1. When I use "shell {session ID}" and run commands I observed behavior in the victim machine terminal where I pasted the payload.

2. After closing the terminal where I pasted the payload, the status of the session becomes undefined and it doesn't work anymore.

I can confirm this behaviour

[t3l3machus]

The shells you can grab with Villain at the moment are not fully functional ptys. If you run commands that start interactive sessions (e.g., nano, cat > file.txt, sh/zsh/bash, vim) your shell will hang. The commands you issue must always return. Maybe its because of that?

[SolsticeSpectrum]

Probably yes, how about creating a service? And running it as a service? That would also mean that it will stay hidden from htop.

[yaseerkhan]

The shells you can grab with Villain at the moment are not fully functional ptys. If you run commands that start interactive sessions (e.g., nano, cat > file.txt, sh/zsh/bash, vim) your shell will hang. The commands you issue must always return. Maybe its because of that?

No that is understandable, but here sessions were the main concern as they get into undefined state after closing the terminal where the payload is executed! let me try to explain it with an example.

I generated a payload for Windows and executed that payload in the Powershell but now when I close that instance of PowerShell the session status changes to undefined state and that specific session is not usable any further

I hope this example helps you get an idea of what i was talking about initially!!