kavika13/RemCom

Remcom services left behind

rustyscottweber opened this issue · 0 comments

Currently, there is a problem with remcom service. If you run the service and then something happens where you are unable to remove the service, for example: a reboot, the service is leaked and tends to clutter up the service console and registry. Since certain tools like impacket python module will spawn lots of remcom services all with a randomly generated name for each service this tends to be a problem. It sounds like it would be a good idea to have just one service which can spawn multiple processes and letting this service start with the machine, but I am not sure how feasible this idea is.