You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How was the implant created? Created using scarecrow with donut shellcode x64
Defensive Technologies
Is the target environment running any particular defensive products? Defender, Carbon Black Cloud.
To Reproduce
Steps to reproduce the behavior:
Create new fcomm implant
run commands over a period of time on fcomm implant.
Expected behavior
last seen time within implant handler updates to show the time that fcomm last successfully communicated. - This does not occur, last seen time remains stuck at "initialisation" time.
Screenshots
Attach files if required
Additional context
I think this could be related to some of the side improvements to the implant handler brought in as part of the FComm branch.
The text was updated successfully, but these errors were encountered:
Description
A clear and concise description of what the bug is.
Execution Environment:
All of this must be filled in
Implant Info
Defensive Technologies
To Reproduce
Steps to reproduce the behavior:
Create new fcomm implant
run commands over a period of time on fcomm implant.
Expected behavior
last seen time within implant handler updates to show the time that fcomm last successfully communicated. - This does not occur, last seen time remains stuck at "initialisation" time.
Screenshots
Attach files if required
Additional context
I think this could be related to some of the side improvements to the implant handler brought in as part of the FComm branch.
The text was updated successfully, but these errors were encountered: