A small solution for Linux emergency disposal

之前又个客户说自己的linux机器有，活动链接数大，CPU高的特点。 客户初步处置：断网，下线，重启。 我给他们提了个处置步骤，结果就没下文了。。。。。

The recommendations are as follows:

(0) View History command, recently opened file.
(1) Confirm the server daily application, application process name, file path, process open port.
(2) View active process, process open file, memory string information, privileged user.
(3) Viewing network links, establishing linked network conditions, monitoring network conditions
(4) Check the user login situation, the recent log, login user name, login IP.
(5) Check the boot, virus in order to be able to start the host system multiple times, there will always be self-booting.
(6) The planning task, one of the self-priming techniques, is found in mining-type viruses.
(7) Critical directory troubleshooting, System tmp directory, VAR and other long-standing path of suspicious files under the investigation.
(8) Open port, check open port, see if there are abnormal ports, often used for virus communication.
(9) Security log, System log, application log and other queries, look for exceptions from the log file.
(10) Comprehensive file export, using anti-virus software scanning avira.
(11) Using MD5 value comparison, the file is exported to calculate hash and normal system file hash comparison, check out the problematic file.
(12) Review the application, patch situation, check whether the vulnerability caused by the intrusion of the server problem, look for other possible intrusion traces.
(13) Audit account information, already have account status, privileged account.
Rootkit check, some malicious code using process and other hidden means is not easy to check out, using the Rootkit Check tool.
(14) Obtain a detailed analysis of the sample after the abnormal sample.

A small solution for Linux emergency disposal