1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

HELP! How do I stop QMAIL hijacking by Spammer/HAcker? Calling for Jamesyeeoc!

Discussion in 'Plesk for Linux - 8.x and Older' started by criticman, Dec 17, 2005.

  1. criticman

    criticman Guest

    0
     
    Quick question for you Jamesyeeoc:

    Someone, supposedly from Brazil, has managed to flood my server with attempts to send spam.

    I have gone through what you have said in other posts, as well as ART's posts. I have installed qmHandle. I had 400,000+ yesterday that I deleted with qmHandle.

    I have set queuelifetime at 50,000.

    I have added the "from" address to badmailfrom, but since they are spoofing it keeps getting through. Although, it still appears the same e-mail address is being used in the "From" .

    GoDaddy has shut down my outgoing mail traffic, but the "hacker/spammer" is able to keep attempting the sending of mail.

    Here is a header from a spam message:

    Code:
     --------------
    MESSAGE NUMBER 157508509 
     --------------
    Received: (qmail 27782 invoked by uid 2520); 17 Dec 2005 11:48:27 -0700
    Received: from 127.0.0.1 by lonetreehosting.prod.phx1.secureserver.net (envelope-from <anonymous@lonetreehosting.com>, uid 48) with qmail-scanner-1.25st 
     (clamdscan: 0.87.1/1211. perlscan: 1.25st.  
     Clear:RC:1(127.0.0.1):. 
     Processed in 0.150098 secs); 17 Dec 2005 18:48:27 -0000
    Date: 17 Dec 2005 11:48:27 -0700
    Message-ID: <20051217184827.27462.qmail@lonetreehosting.com>
    content-type: text/html
    Subject: URGENTE: Verifique seu CPF
    From: [email]Receita@receita.gov.br[/email]
    To: [email]gsmenezes@oi.com.br[/email]
    X-Qmail-Scanner-1.25st: added fake MIME-Version header
    MIME-Version: 1.0

    GoDaddy is sucking presently at fixing this. I am trying to figure it out, but I am not a mail admin pro by any means, so please help.
     
  2. criticman

    criticman Guest

    0
     
    Oh, and I also went through the mail logs yesterday. I could not find a false SMTP connection made at any point yesterday afternoon or evening when this began occurring. All logged SMTP connections were from my valid users and demonstrated that they did valid SMTP auth.

    I did check and see what IP's were sending the most traffic through, GoDaddy blocked the biggest ones, but still happening.

    I also have set each site, through Plesk, to just "Reject" mail to nonexistent users instead of bouncing it.

    UPDATE: Also, I have been using the following command to delete the bulk of the spam attempts since, from what I have seen, they have the same message subject:
    Code:
     ./qmHandle -SURGENTE
     
  3. criticman

    criticman Guest

    0
     
    Stupid GoDaddy has no clue. They let me know an issue occurred way back in September - how, I do not know as I did not open up any ports or undo any security settings, so their initial config was not proper. Even so, they want me to back up "all essential data" so they can wipe it clean. Like I have time (or my clients) to let it all get wiped then reconfigured.

    Any advice would be great. A copy of their message is below.

     
  4. SecondPhase

    SecondPhase Guest

    0
     
    Hi there, i'm not an expert here but i'll throw out some idea that i've read recently around this forum..

    I would guess that a hacker installed this spammer mailer tool on your system using a PHP or Apache security hole probably using the wget command to get this stuff in your /tmp directory.

    First type from the command line:
    chmod 700 /usr/bin/wget
    so only the root user can run this.

    Then search the forum to install / configure Apache mod_security and PHP patches or inits that are more secure..

    I guess it depends whether you think anything else was done to the machine. GoDaddy probably doesn't want to risk it and best to just wipe it out in case other features are compromised (backdoor?) or have virus.. somebody else here may know from the exact description of your problem what else may have happened..

    If it's just a spamming script, deleting it and closing the security hole may be ok for you.. maybe the wget permission will solve it by itself, but i've been reading about other security measures and will be implementing some more of them myself.
     
  5. criticman

    criticman Guest

    0
     
    Well, their efforts were not helpful.

    After their email, I deleted the spam messages from the queue by subject.

    Two hours later, 10,000 more in there.

    Please help!
     
  6. criticman

    criticman Guest

    0
     
    I just chmod'ed wget, chmod 700 /usr/bin/wget

    Will delete queue and see, but I am guessing there is another script on there.

    UPDATE: I do not just trust their changing permissons on those files, so I deleted the spam script and the directory that housed it.

    Hoping it will work.

    Wow, I feel like I am just talking to myself here. If someone wants to chime in, much appreciated.
     
  7. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Sorry I didn't see this earlier, I've been sick with the Flu. Some of the following may not be in good order, still can't think too well due to sick and medications.... :)

    1. GoDaddy will most likely not be of much use, other than a reimage.

    2. They are just now informing you of a malicious script from September????

    3. WGet is not the only way they can upload files to your server, so chmodding wget is of small use, but not a 'cure all'.

    4. Check the /tmp for any other files or hidden dir's (such as .tempe), there may be more than just one.

    5. If they do a server reload, the FIRST THING TO DO before reloading any hosted domain files is to SECURE YOUR SERVER! You should check into ARTs ASL (Atomic Secured Linux) but at the very least install mod_security, your AV of choice, Spamassassin, AND qmail-scanner (also from ARTs site). Also install RKHunter and CHKRootkit and have them cron'd to update and then run scans, optionally email results to you.

    6. Make sure that any exploitable packages (such as phpBB) are updated on your client's sites. All it takes is for one bad package to be installed and it will compromise the entire server.

    7. There is no easy or simple fix.

    8. After deleting the script/directories, YOU MUST MAKE SURE THERE ARE NO PROCESSES RUNNING IN MEMORY which are related to the malicious script. Review your process list carefully.

    9. Install and configure mod_security. The default settings only include a couple of the available rulesets, you may need to add some of the additional ones.

    10. All this 'assumes' that it is most likely an exploit, not a hack/crack or rooting. If I get more coherent and think of anything else I'll post again.

    11. Checking logs for SMTP connections is useless since the emails are originating from within your server (the malicious script), not from 'outside' your server.
     
  8. criticman

    criticman Guest

    0
     
    Awesome, you posted! Sucks that you are sick - I hope you get better soon.

    I did most of your steps above prior to them telling me they were going to wipe it. I was in the process of installing and configuring mod_security, chkrootkit, and rkhunter - found good info on setting it all up thanks to you all on the forums.

    I have backed it all up and told GoDaddy that it is ready for them to wipe. Their claims that it would be quick changed, "process will be taken care of in 24-48 hours."

    But yes, once they wipe it, I will setup the security provisions prior to putting client sites back on there.

    I think I may invest in setting up a secondary server with Godaddy, so if this happens again I can mod DNS to point to it while the other one is down. Think this is a worthwhile investment? Sure beats stepping up to "the big boy" hosting, such as rackspace...although with them it would never have happened and I could've finished several PHP projects this weekend.
     
  9. phatPhrog

    phatPhrog Guest

    0
     
    mod_security

    You should go to http://gotroot.com and grab the up-to-date rules written there. (thank you ART and assoc.)

    Also, there is a script available at gotroot that will automatically update the mod_security rules. I edited and added to it so all of the available rules are updated.

    The original script checks and rolls back to last updates if the new ones cause apache problems.

    You can run the update script manually or set it up as a cron.

    If, after you grab the original script from gotroot you'd like to have my edited version, let me know and I'll send it.

    Works great for us.

     
  10. criticman

    criticman Guest

    0
     
    Well ****....so I was rushing to get it backed up....and I failed to make the shell map file and IP map files.

    So, any quick way to fix this? I found the format on PSA website. I will just have to manually configure my entire configuration (luckily only 29 domains) unless someone has another way.
     
  11. phatPhrog

    phatPhrog Guest

    0
     
    The map file is created in the restore process:

    Just run:

    cat dump.* | /usr/local/psa/bin/psarestore -m map_file -s shells_map_file -f -

    then run

    /usr/local/psa/bin/psadump -F -f $backupdir/dump2_$date.svr

    in whatever name convention you use for your backups.
     
  12. criticman

    criticman Guest

    0
     
    I did this, and bingo, made the files. When I try to run the restore now using those files, it is throwing this error:
     
  13. criticman

    criticman Guest

    0
     
    Here is the ip_map_file contents:
     
  14. phatPhrog

    phatPhrog Guest

    0
     
    First, how did this topic end up being about backup/restores? Thought you were having problems with hijacking?

    Hope we don't get yelled at for straying off subject here. :p

    Anyway, I'll close up here by saying we run a script for our backup/restores, and the following map creation and restore works without error for us.

    If you run the following first;

    cat dump.* | /usr/local/psa/bin/psarestore -m map_file -s shells_map_file -f -

    then;

    /usr/local/psa/bin/psarestore

    FROM the directory where your dump file resides you should have no problem with a restore.

    This of course depends on whether you have a working server. The dump doesn't backup the entire server.

    We're gonna get smashed by continuing this conversation off topic.

    Believe me, I know; 'cause my history proves off-topic subjects. :rolleyes:

    Just trying to help.
     
  15. criticman

    criticman Guest

    0
     
    Heh. I started the topic, so people can get bent if they feel the need to complain. This is all an ongoing issue I am trying to get help with.

    Server is indeed working. So that method will create the needed map files that actually work? I will try, because I keep getting the same error with the info used above.
     
  16. criticman

    criticman Guest

    0
     
    No luck:
     
  17. criticman

    criticman Guest

    0
     
    Tweaking more, now getting this issue....

    UPDATE: GOT IT! Typo...I had username with initial on one...removed, all good now...or at least it is running the restore!
     
  18. criticman

    criticman Guest

    0
     
    So apparently the key they put into plesk when they wiped it was not proper. So, copied restored key over, then going back and redoing the restore after I reboot....
     
  19. criticman

    criticman Guest

    0
     
    DONE!

    Thanks everyone for your help! Time to secure the **** out of the server even more!
     
  20. nhouse

    nhouse Guest

    0
     
    Hello everyone... I am unfortunately having the same issue that was stated in the beginning of this thread. Only my spammer comes across as mensagens@namorando.com.br and another one or two varients with similar addresses. criticman, did you or anyone else here find out an answer from GoDaddy or elsewhere? I did some Googling and came up with a rederence or two to it possibly being the result of a virus. See these links to review:
    Symantec Site
    Trend Micro Site

    Ok, with that said... if one of my clients has a virus on their system (maybe one at home, etc.) then I suppose it couple be possible that the virus has somehow "grabbed" their smtp server settings and is mass mailing from their machine. Does this sound logical? I do have a virus scanner on my server (virtual dedicated) but I also guess that it wouldn't catch outbound virus / spam activity.

    Anybody found similar types of issues or maybe a solution? Also, can you give me tips on how or what to look for in the log files that would assist me. So far I can't spot anything that looks off. I see lots of these:

    Feb 26 12:14:07 nhousemedia qmail: 1140977647.369362 starting delivery 6393: msg 227648526 to remote joaol@claretianas.com.br
    Feb 26 12:14:07 nhousemedia qmail: 1140977647.369879 status: local 0/120 remote 117/120
    Feb 26 12:14:07 nhousemedia qmail: 1140977647.370403 starting delivery 6394: msg 227647928 to remote joao@ixp.com.br
    Feb 26 12:14:07 nhousemedia qmail: 1140977647.370883 status: local 0/120 remote 118/120
    Feb 26 12:14:07 nhousemedia qmail: 1140977647.371472 delivery 6383: success: 64.202.189.86_accepted_message./Remote_host_said:_250_ok_1140977646_qp_23890/
    Feb 26 12:14:07 nhousemedia qmail: 1140977647.371959 status: local 0/120 remote 117/120
    Feb 26 12:14:07 nhousemedia qmail: 1140977647.372446 end msg 227648512


    Can you folks spot any obvious things here? It looks like they are being authenticated by someone... but who? Is there a way to find out the IP address of the sender... or if it local, the exact email user???

    Any help would be VERY much appreciated. This **** has happened twice over the weekend with one occasion the queue ranging up to 155,000 messages in the remote and 22,000 in the local... this killed xinietd and qmail crashed.
     
Loading...