At about 10 o’clock this morning, I logged in to the server to check related items. Unexpectedly, the login page was stuck directly and couldn’t connect. I finally found out that the command input card is not needed. Look at the CPU. Fuck! Fuck! Fuck! I How can it be 100% without running any programs? ? ? (Personal, non-company, no program running) Hurry up and log in to the Alibaba Cloud console to find out, 
fucking? I was so scared that I hurriedly clicked in and 
took a look at this tm's day dog! ! ! ! ! ! It was a long torment to enter the Aliyun web console quickly. After waiting for a long time, I finally entered, but it was useless. The command card didn't come out, so angry. There is no way but to restart and use a little gap time to enter the console. Okay, don't talk nonsense, just talk about the solution steps:
1: top View the CPU usage and process as follows: 
java64? What the hell is this tm? Actually disguise the java process, why is it disguised? Because I use docker for environment isolation, there is no java environment on the cloud server! MMP I believe in you a ghost, you are a bad old man!
2: cd /proc/pid such as
Found the file where the execution program is located and then enter the /var/tmp directory
3：cd /var/tmp/ && ll 
Damn it? What are you waiting for directly rm rm rm MMP
4: rm rm rm kill process kill process pkill java64 pkill basdd Note: The system is still not rm, it seems to be Alibaba Cloud. .
I thought it was done, but it didn't work. The file came out again after a while? ? ? Oh, so angry. What's the matter? It won't be a scheduled task, so hurry up and check it out
5：crontab -l
Voj? ? ? Sure enough, the script is not serious, has been downloading the startup grass, and quickly kill it
6：crontab -r
Turn off the timed task here, and repeat the previous steps (because it is useless to delete the directory before, the script keeps running, the file deletion is not clean, and the mining process is also running)
Is the world peaceful again? I waited for more than half an hour, 
MMP was finally relieved.
The above is the solution process, here you can optimize the next steps:
1 View timing tasks crontab -l
2 Delete the mining timing task crontab -r
3 View resource usage top
4 View the path where the command is located cd /proc/{pid} & ll
5 Delete script rm rm rm
6 Kill processes in batches pkill java64 pkill basdd
7 Finish cleaning up the mining script