Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Long running modules lock up agents #16
[Version] 2.5 BC-Security Fork
OS Information (Linux flavor, Python version)
Python 2.7.16, Kali GNU/Linux, version 2019.2
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
Expected behaviour: An agent runs a long running job. The agent continues to beacon back to C2 server, and the agent can run other jobs while the first job runs in the background.
Actual behaviour: The agent starts a long running job. The agent no longer beacons back to the C2 server, and an operator can no longer interact with the agent.
Screenshot of error, embedded text output, or Pastebin link to the error
No screenshot, but tested a few long running modules, including
Any additional information
Agent running on Windows 10, PSversion 5.1
Been spending some time trying to isolate the issue. The Empire 2.5 master branch runs without locking up the agent but this bug is also present in the Empire 2.5 Dev branch. That also coincides with some updates to agent.
My best guess right now is that an update broke the multi threading as the agents continue to run through the module logic loops. They just become unresponsive both on the compromised host and to the C2 server