In Centos 7, it was enough to put these lines in the csf.pignore file:
Code: Select all
exe:/usr/bin/spamc
exe:/usr/bin/spamd
cmd:spamd child
Since Centos 8 this is change, no clue as to why.
On is about a suspicious process, the other one about excessive resource usage.
This is the one about suspicious process:
Code: Select all
Time: Tue Nov 17 17:43:13 2020 +0100
PID: 1220390 (Parent PID:1220388)
Account: accountname
Uptime: 52384 seconds
Executable:
/usr/bin/perl
Command Line (often faked in exploits):
spamd child
Network connections by the process (if any):
tcp: 127.0.0.1:783 -> 127.0.0.1:47734
udp: 127.0.0.1:63011 -> 127.0.0.1:53
Code: Select all
Time: Tue Nov 17 17:43:13 2020 +0100
Account: accountname
Resource: Process Time
Exceeded: 52384 > 1800 (seconds)
Executable: /usr/bin/perl
Command Line: spamd child
PID: 1220390 (Parent PID:1220388)
Killed: No
We can stop this by adding the perl executable to csf.pignore but it's better to keep monitoring perl.
This issue is only occuring on Centos 8 servers, not on Centos 7 servers.
Configuration of csf.conf and csf.pignore is exactly the same on all servers.
I'm not the only one experiencing this.
System.
OS Centos 8.2.2004
Directadmin