Support

Admin Tools

#12412 How bad is this breach?

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by nicholas on Thursday, 24 May 2012 14:56 CDT

finack
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting. Yes
Joomla! version: 2.5.4 Stable
PHP version: 5.3.9
MySQL version: 5.1.62-cll
Host: Rochen
Admin Tools version: Deluxe/Pro 2.2.5

Description of my issue:
Hello, Nicholas your tools are very intuitive and very, very well documented. You've put much thought into your tools and documentation. Thank God for you. Your expertise and skills are apparently top notch. I wish I would have taken your advice sooner instead of snoozing at the wheel, so to say.

Just a little background info first. Hind site is 20/20. It's time to get PROACTIVE with security. I've been building Joomla sites for a few years, more or less, to help some of the small businesses that I work with, and I'm making next to nothing so I haven't been motivated to take yet more time to dive into security and the people I've helped know this. But I'm starting to find more and more people are asking for my help and I can actually make some money, so I'm taking this very serious now as I will be becoming a Rochen reseller very soon. I live in a retirement community and we have many small businesses that want a web presense.

Anyways... The same site that I just rebuilt at the beginning of the year (was running Joomla 1.5.25) was hosting a hacked subsite that went un-noticed for some time, and appears to have had a similar breach after doing a complete fresh install of Joomla 2.5 with minimal extesnions. Upon doing some updates to Joomla and extensions for one of our customers (the one mentioned above), I noticed that while I was in Cpanels file manager that there was a "sonographers" directory in the root of "public_html", containing a "cream.php" script of some sort, of which, I can't make heads or tails of because I'm not a PHP programmer. I also noticed that the timestamp on the .htaccess file in the root of "public_html" was also modified on the same date and time that the "sonographers" directory and accompanying script were created. After futher research, I started to get very worried, as the info I found from others that had a similar script running had their .htaccess files modified to redirect visitors to malicious websites. I don't see similar entries in the .htaccess file that was modified but am unsure as everthing is cryptic even after reading up on how .htaccess rules/statements work in general.

I removed the "sonographers" directory and files. I've purchased the Delux Akeeba tools and installed them, read through the docs and configured the Web Application Firewall and run the .htaccess maker. I just hope it's not to late for this customer.

Notes on the new Joomla instalation:
The original .htaccess file on this server was automatically created when Joomla 2.5x was installed via the Rochen Joomla auto-installer utility that Rochen offers, of which Nicholas helped develope I believe, a while back. But from what he told me, that .htaccess file was for Joomla 1.5x, not the newer versions of Joomla.

I've scoured logs and looked through all the directories for suspicious looking files and corresponding timestamps, file persmissioin, spikes in bandwidth usage, etc..etc.. Before installing the Akeeba Admin Tools. But I'm new to this and can't tell if this breach was stopped some way durning the excalation process or is lying hidden and alive right under my nose. I would appreciate if someone can take a look at the modified .htaccess file and cream.php script and tell me what I should be looking for possbily. I've spent hours upon hours reading, sifting through logs and code that makes no sense to me and it's time I ask for some guidance from the experienced pro-active security conscious Joomla users.

Please help a guy that wants to help himself and his customers and learn some best practices. If someone is willing to look at these files, let me know the best way to deliver them.

Thanks for your time,
Joshua

nicholas
Akeeba Staff
Manager
Hi Joshua,

That breach had occurred a long time ago. Any possibility to trace its origin is now long gone as you deleted the original file (which would give us a timeframe for the breach) and the logs have already been rotated. In any case, if you use Admin Tools' .htaccess Maker then the generated .htaccess will make sure that such a file would not get executed anyway. Since you've already done a lot of searching, I believe that you have most likely removed all traces of the malicious script from your site.

For more information on doing post-breach forensics and securing your site you may want to read the Unhacking your Site walkthrough. It's a good idea to read that before you get hacked, so that you know what you have to do.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

finack
Hi Nicholas,

Thanks for the response and the link. I have it bookmarked for reading today.

Actually the site was compromised twice. The first time we noticed was last year when they were running Joomla 1.5.25. The fix was to completely wipe the site out and reinstall fresh with Joomla 2.x. This time around I decide to try out Rochen's Joomla Auto Installer utility. The onef that auto created the .htaccess that you created.

That's when I got in contact with you before about this particular customer wanting their favicon to show up and you helped me modify the .htaccess file to allow it.

That's also when I decided to purchase the Akeeba Deluxe subscription as I didn't want this to happen again on any site I built in the future. Long story short that customer declined to make their final payment to me so I never installed the tools on their site. They made final payment last week and so I went back into their site to do some routine maintenance and that's when I noticed that had another breach. Not nearly as bad as last time from what I can tell, but another breach none the less.

I did download a backup off of Rochen Vault before I did anything so that I might learn for myself. I wasn't wanting or expecting anyone to take time to do site forensics or anything like that.

I just wanted someone with .htaccess and php programming know how to take a quick glance at the .htaccess file that was modified, to see if they notice anything glaringly nasty (there's not much there)as well as taking a quick look at the cream.php script to see what it is that script was trying to do.

Is that something you could take a quick peak at? I'm sure you'll know within a minute, it's not much code at all, what they were accomplishing or hoping to accomplish. If this isn't something you're willing to do, I totally understand. I'm just curious as to the possible seriousness of the breach. I would think if you have the ability to modify a .htaccess file then it's pretty much game over right?

Either way, thanks for your time Nicholas. I value it. Much appreciated.
Joshua

nicholas
Akeeba Staff
Manager
Actually the site was compromised twice.

This means that the hack file was left behind.

This time around I decide to try out Rochen's Joomla Auto Installer utility. The onef that auto created the .htaccess that you created.

That file is seriously outdated. It's over 2 years old and my Master .htaccess has gone through a dozen revisions since :)

That's when I got in contact with you before about this particular customer wanting their favicon to show up and you helped me modify the .htaccess file to allow it.

Right! I remember that contact! I was surprised that someone had contacted me after so much time since I last did any work for Rochen :)

and that's when I noticed that had another breach. Not nearly as bad as last time from what I can tell, but another breach none the less.

This thing sounds like there are outdated extensions installed on the site or there are leftover hacking scripts which are used to breach the site.

I did download a backup off of Rochen Vault before I did anything so that I might learn for myself. I wasn't wanting or expecting anyone to take time to do site forensics or anything like that.

OK, you now know for the next time: first collect the evidence, find the root cause, fix it. Otherwise, at best you are just reverting your site to its previous, vulnerable state and it will be hacked all over again.

I just wanted someone with .htaccess and php programming know how to take a quick glance at the .htaccess file that was modified, to see if they notice anything glaringly nasty (there's not much there)as well as taking a quick look at the cream.php script to see what it is that script was trying to do.

I can tell you right from the start what the script does, without looking at it. It has some base64_decode stuff in there which are deeply nested. In the end it either serves links to warez/porn/drugs, distributes malware or is used to remotely control other hacked sites. It's typical MO for for-profit hackers.

I would think if you have the ability to modify a .htaccess file then it's pretty much game over right?

That's right. Well, you can send me the file. In order to do that, rename it to .txt, put it in a ZIP file and attach the ZIP file here.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!