jm33-m0 / emp3r0r

Linux/Windows post-exploitation framework made by linux user
https://infosec.exchange/@jm33
MIT License
1.26k stars 232 forks source link

Need Custom Agent Tag #19

Closed Error996 closed 3 years ago

Error996 commented 3 years ago

Need Custom Agent Tag Or Add Custom Agent Label

Because once the Agent exceeds a certain number, it will be difficult to identify

Good Job

jm33-m0 commented 3 years ago

Yeah it would be nice to have custom tagging, I will try to implement it in build.py so we can name each agent on its birth.

Error996 commented 3 years ago

yep,or add a lable like vultr.com

Error996 commented 3 years ago

Lable exists on CC, it is better to set on CC,Just suggest

jm33-m0 commented 3 years ago

Lable exists on CC, it is better to set on CC,Just suggest

Then we need a file to record label -> UUID mapping, and a set of commands to update the file. Sounds like a lot more work to do, I will try to implement the mapping file first. Thanks for the advice.

Error996 commented 3 years ago

i have an other question,dose CC Indicator must be "emp3r0r" ????

jm33-m0 commented 3 years ago

Yeah, for now it's emp3r0r. But with HTTPS, there's no need to change this value, they will be encrypted anyway.

It's trivial to use custom value via build.py, and modify the source accordingly. If you feel this is necessary, you can implement that yourself, and you are always welcome to send a PR to this repo.

Error996 commented 3 years ago

I modified and used libemp3r0r.so, but all files have been hidden, but the process can still be seen, whether it is ps -ef or netstat -anptl 20210308135151 20210308135225 20210308135247

Error996 commented 3 years ago

20210308135436

Error996 commented 3 years ago

sorry,i konw how

jm33-m0 commented 3 years ago

Okay, next time open a new issue instead.

jm33-m0 commented 3 years ago

Fixed in https://github.com/jm33-m0/emp3r0r/commit/e23d7c1c5132f73340fc6580a5a7dc3e8b93b8d7