Suspicious File Alert mail every night

Started by thomash, October 08, 2015, 09:21:02 PM

Previous topic - Next topic

thomash

Hello.

Can someone tell me why I get those mails every night?

What can I do to prevent this, and is it something that I need to worry about?

Time:   Thu Oct  8 00:05:09 2015 +0000
File:   /tmp/apache-build/apr-1.5.1/configure
Reason: Script, starts with #!
Owner:  : (1000:1000)
Action: No action taken

Time:   Thu Oct  8 00:05:09 2015 +0000
File:   /tmp/apache-build/apr-1.5.1/buildconf
Reason: Script, starts with #!
Owner:  : (1000:1000)
Action: No action taken

Time:   Thu Oct  8 00:05:09 2015 +0000
File:   /tmp/apache-build/apr-1.5.1/apr-config.in
Reason: Script, starts with #!
Owner:  : (1000:1000)
Action: No action taken

Time:   Thu Oct  8 00:05:08 2015 +0000
File:   /tmp/apache-build/suphp-0.7.1/config/ltmain.sh
Reason: Script, file extension
Owner:  : (1000:1000)
Action: No action taken

Time:   Thu Oct  8 00:05:08 2015 +0000
File:   /tmp/apache-build/suphp-0.7.1/config/install-sh
Reason: Script, starts with #!
Owner:  : (1000:1000)
Action: No action taken

Time:   Thu Oct  8 00:05:08 2015 +0000
File:   /tmp/apache-build/suphp-0.7.1/configure
Reason: Script, starts with #!
Owner:  : (1000:1000)
Action: No action taken

Time:   Thu Oct  8 00:05:08 2015 +0000
File:   /tmp/apache-build/suphp-0.7.1/config/config.sub
Reason: Script, starts with #!
Owner:  : (1000:1000)
Action: No action taken

Time:   Thu Oct  8 00:05:08 2015 +0000
File:   /tmp/apache-build/suphp-0.7.1/config/config.guess
Reason: Script, starts with #!
Owner:  : (1000:1000)
Action: No action taken

Time:   Thu Oct  8 00:05:08 2015 +0000
File:   /tmp/apache-build/suphp-0.7.1/config/depcomp
Reason: Script, starts with #!
Owner:  : (1000:1000)
Action: No action taken

Time:   Thu Oct  8 00:05:08 2015 +0000
File:   /tmp/apache-build/suphp-0.7.1/config/missing
Reason: Script, starts with #!
Owner:  : (1000:1000)
Action: No action taken

Regards
Thomas.

Glenn


thomash

No. The crew here at CWP installed and compiled CentOS, and I have not recompiled it afterwords..

/Thomas.

Administrator

you can simply delete this files, but you should be careful with this command as you could end-up with your server deleted.
rm -Rf /tmp/apache-build/



AntiDDoS Protection (web + mail)
http://centos-webpanel.com/website-ddos-protection-proxy


Join our Development Team and get paid !
http://centos-webpanel.com/develope-modules-for-cwp





Services Monitoring & RBL Monitoring
http://centos-webpanel.com/services-monitor











Do you need Fast and FREE Support included for your CWP linux server?
http://centos-webpanel.com/noc-partner-list
Installation Instructions
http://centos-webpanel.com/installation-instructions

Get Fast Support Here
http://centos-webpanel.com/support-services

misterpat

Will this work for php-build also in the tmp directory?

File:   /tmp/php-build/php-5.4.45/*

Administrator




AntiDDoS Protection (web + mail)
http://centos-webpanel.com/website-ddos-protection-proxy


Join our Development Team and get paid !
http://centos-webpanel.com/develope-modules-for-cwp





Services Monitoring & RBL Monitoring
http://centos-webpanel.com/services-monitor











Do you need Fast and FREE Support included for your CWP linux server?
http://centos-webpanel.com/noc-partner-list
Installation Instructions
http://centos-webpanel.com/installation-instructions

Get Fast Support Here
http://centos-webpanel.com/support-services

crmgddn63

File:   /tmp/apache-build/httpd-2.2.27/server/core.o
Reason: Linux Binary
Owner:  root:root (0:0)
Action: No action taken

i give this message every hour. how can i fix this ?

Neo2SHYAlien

#7
Append at the end of /etc/csf/csf.fignore those 2 rows
/tmp/apache-build/.*
/tmp/php-build/.*

After that restart lfd and everything will be ok :) I prefer this approach will be better if is added as CWP CUSTOM rules as as the rows in /etc/csf/csf.pignore
"Would you tell me, please, which way I ought to go from here?"
"That depends a good deal on where you want to get to," said the Cat.
"I don't much care where–" said Alice.
"Then it doesn't matter which way you go," said the Cat.
Neo2SHYAlien's Blog

crmgddn63


johnhelmer

Quote from: Neo2SHYAlien on March 20, 2016, 02:02:07 PM
Append at the end of /etc/csf/csf.fignore those 2 rows
/tmp/apache-build/.*
/tmp/php-build/.*

After that restart lfd and everything will be ok :) I prefer this approach will be better if is added as CWP CUSTOM rules as as the rows in /etc/csf/csf.pignore

Can you just add these two lines as is to pignore or does it require a different format?

Neo2SHYAlien

Quote from: johnhelmer on March 26, 2016, 10:59:29 PM
Can you just add these two lines as is to pignore or does it require a different format?

You should add them to /etc/csf/csf.fignore not ot pignoner file. pigone is for process ignoring respectively fignore for file ignoring rules :)
"Would you tell me, please, which way I ought to go from here?"
"That depends a good deal on where you want to get to," said the Cat.
"I don't much care where–" said Alice.
"Then it doesn't matter which way you go," said the Cat.
Neo2SHYAlien's Blog