Skip to main content

High CPU apache nobody

Comments

5 comments

  • Jcats
    Are you running DSO? If yes, you may want to run easyapache and select mod_ruid2 as it will allow the processes to run as the cPanel user. You can use LSOF to help as well, example:
    # lsof -p 15732 |grep /home httpd 15732 CPUSER 48r REG 182,193729 321284 1460018 /home/CPUSER/public_html/domain.com/themes/default-bootstrap/cache/v_47_1de9935608a5fce3cc504e3fd414df59.js
    You can also tail all domlogs and see if any are being spammed, from what you posted it looks like someone is spamming the xmlrpc.php
    # tail -f /usr/local/apache/domlogs/*/*
    On our shared servers, we disable access to xmlrpc.php globally except for Jetpack, if you go to WHM > [LIST]
  • Home "
  • Service Configuration "
  • Apache Configuration "
  • Include Editor Then select "Pre VirtualHost Include" and put in:
    Order Deny,Allow # Whitelist Jetpack/ Automattic CIDR IP Address Blocks Allow from 192.0.64.0/18 Allow from 209.15.0.0/16 Allow from 66.155.0.0/17 Deny from all
    This will stop the attack and prevent it from happening on all sites.
  • 0
  • Eric
    Howdy, What versions of apache/php/wordpress are you using? Also it's not a bad idea to strace one of those run away apache processes to find out what's going on. Thanks!
    0
  • tank
    I am running suphp and php version 5.5.30. The versions of wordpress are all different. Some are up to date some are not. I tailed the logs and and it looks like they are not being spammed. It just looks like this process just sits there using resources. I am going to add the include editor like you suggested. Thanks I tried to do a strace and got:
    # strace -p 164328 Process 164328 attached - interrupt to quit
    Thanks guys
    0
  • garconcn
    I've seen this for a while. This is more likely an xmlrpc amplification attack. Brute Force Amplification Attacks Against WordPress XMLRPC - Sucuri Blog If you search the attacker IP, you will see another POST a few minutes before the xmlrpc.php. The 1st POST size is big, I suspect it contains many username/password combinations. In 2nd POST, it just brute force the login until tried all combinations. The process seems do not exit after it finish. If you strace the process, you probability see no activity. You can only catch it when it just start. Besides xmlrpc attack, I saw some other nobody process can use high CPU.
    0
  • tank
    Thanks guys I appreciate it. The fix of not allowing access to that file except by jet back worked great.
    0

Please sign in to leave a comment.