Commentary

Allen Stern
 

I've Been Exploited

Earlier this week, I converted my main blog from the Drupal content management system to Wordpress. Within 24 hours, I was exploited.

Earlier this week, I converted my main blog from the Drupal content management system to Wordpress. Within 24 hours, I was exploited.I made the decision a couple of weeks ago to move from Drupal to Wordpress for a number of reasons. The process to convert the site wasn't easy and I am working on a technical guide which I will publish later this month. Most of the issue was centered around the URL structure. Drupal has a more complex URL structure which basically broke about 1,000 blog posts which I have been slowly cleaning up the last three days nearly non-stop.

During my URL correction work, I noticed that the blog homepage was shifted to the left. I knew I didn't change the template but since I just completed the template transition to the Wordpress specifications, I started to investigate the shift. After some initial template checks, I looked at the source of the page and am pretty sure I lost several heartbeats. Inside the code of the page were about 250 spam URLs injected into the page.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I had a friend help me diagnose where the spam injection was inside my files and it turned out to be in the overall Wordpress header file. We cleaned it out, changed all of the passwords and re-installed a clean Wordpress installation. The total time the spam injection was live on the site was about two hours.

That amount of time was enough for all of the major search engines to index the updated site with the spam URLs. This has caused Google to flag my blog as "potentially malicious" and I am unsure what it has done to my search rankings but I know my traffic is down significantly. I have started to work on getting it corrected by submitting a "re-inclusion request" via the Google Webmaster tool. I am not sure how long it will take to get this notation removed but they note it could take some time.

Next week I will speak with my web host to learn the technical reasons that this exploit happened. It appears that it was a combination of a file upload and some shell commands.

This is a good example of why it's so important to monitor your site in real-time. You can quickly see incoming traffic patterns and take appropriate action as needed. In my case, I started receiving traffic from MSN Search for some of the keywords in the spam URLs. This tipped me off that there was something weird beyond the template issue I noted above.

At the end of the day, I am glad I switched platforms and eventually Google will help me get the malicious notation corrected. Please use my bad luck as your reason to go and check your blog to make sure you are current in updates and patches. Also check out my guide for creating a backup of your website or blog -- this will help if your site is exploited or compromised.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links