When going through the Oilrig scenario, in step 3 the fsociety.dat is not uploaded to the control server after submitting the 102 command, here reproduced with a test file, the agent doesn't respond after the 102 command:
We tried with several different files, and do not see any POST request from the agent, unless the file doesn't exist, in which case it responds correctly with an error message. From the SideTwist agent or control server code, it is unclear why this should be happening for uploads.
Steps to reproduce:
run controlServer on the Kali VM
add scheduled task with SideTwist agent on the workstation
create a file on the workstation to be uploaded, or use the output file of Valuevault, fsociety.dat in %APPDATA%
run ./evalsC2client.py --set-task toMM '103 FILE_TO_DOWNLOAD'
check content of files folder and output of controlServer
Hi,
When going through the Oilrig scenario, in step 3 the fsociety.dat is not uploaded to the control server after submitting the 102 command, here reproduced with a test file, the agent doesn't respond after the 102 command:
We tried with several different files, and do not see any POST request from the agent, unless the file doesn't exist, in which case it responds correctly with an error message. From the SideTwist agent or control server code, it is unclear why this should be happening for uploads.
Steps to reproduce:
./evalsC2client.py --set-task toMM '103 FILE_TO_DOWNLOAD'filesfolder and output of controlServer