[BUG] Invoke-PSRemoting block current agent

[mpgn]

Empire Version

• Empire 3.5.1

OS Information (Linux flavor, Python version)

• OS: linux
• Python: 3.8

Describe the bug

Maybe not a bug, maybe yes.
When running Invoke-PSRemoting, a new agent pop and it's working fine. But the current agent is blocked and cannot be used unless the new agent is killed.
Is there any workaround for this so the first agent is not blocked waiting for the Invoke-PSRemoting to finish ?

To Reproduce

From agent 1 run Invoke-PSRemoting

Expected behavior

Agent should not be blocked, maybe the Invoke-PSRemoting should be run as a job.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

[Cx01N]

You need to be running empire in Python 3.
Also, can you please provide more information (Empire version, Listener, Stager, what lateral settings and target info)?

[mpgn]

• http listener
• hta stagers

The agent is running on a windows 10 latest version. The module does work, but the inital agent is no responding after that.

The log show this when running the module

[mpgn]

I think I understand why.

I had one agent (agent 1) and wanted to pop another agent so I did in the console Start-Job { powershell xxxx }
From the new agent (agent 2) I run the Invoke-PSRemoting and maybe this is why it failed

I simplify the poc

1. I start a listener
2. I create a HTA stager
3. Agent connect to Empire
4. I run the module Invoke-PSRemoting with proxy settings configured
5. New agent pop
6. the inital agent is stuck, if I exit the new agent, the initial agent is back to life again