• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Apache Postfix botnet Spam?

Jayson

Basic Pleskian
Hello,

I have seen lots of spam in my postfix queue coming from apache with no php script listed.

Jan 30 14:48:09 majestic postfix/qmgr[29260]: D11DEECD1F1: from=<>, size=11154, nrcpt=1 (queue active)
<[email protected]>, relay=none, delay=0, delays=0/0/0/0, dsn=5.0.0, status=bounced (User unknown in virtual alias table)

I can't find what script is responsible for sending it. I have looked through the maillog and access_log (apache) without luck.


Can anyone suggest how to locate an offending script, or perhaps how to block this?

Thank you,
 
31.184.244.18 - - [22/Jan/2013:02:03:28 -0800] "POST /.e13d.php HTTP/1.1" 404 433 "-" "-"
31.184.244.18 - - [22/Jan/2013:02:03:30 -0800] "POST /anon_ftp/.e13d.php HTTP/1.1" 404 442 "-" "-"
31.184.244.18 - - [22/Jan/2013:02:03:36 -0800] "POST /.6645.php HTTP/1.1" 404 433 "-" "-"
31.184.244.18 - - [22/Jan/2013:02:03:38 -0800] "POST /cgi-bin/.6645.php HTTP/1.1" 200 622 "-" "-"
31.184.244.18 - - [22/Jan/2013:02:03:49 -0800] "POST /.81c8.php HTTP/1.1" 200 61434 "-" "-"

31.184.244.18 - - [22/Jan/2013:06:39:30 -0800] "POST /.81c8.php HTTP/1.1" 200 190 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120421 Firefox/11.0"


Is there some way I can prevent this because these log entries don't tell me what actual script was exploited to get this php file on my server.

Regards,
 
Back
Top