<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Hackers Attack &amp; Stats Drop: Your WordPress Blog Could be a Victim</title>
	<atom:link href="http://agbeat.com/g-rants-insanity-more/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/feed/" rel="self" type="application/rss+xml" />
	<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/</link>
	<description>News, insights, tools, and inspiration for business owners and professionals</description>
	<lastBuildDate>Fri, 10 Feb 2012 15:13:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Braxton Beyer</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-31958</link>
		<dc:creator>Braxton Beyer</dc:creator>
		<pubDate>Fri, 01 May 2009 04:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-31958</guid>
		<description>@SQL Tutorials: you could try something like Amazon&#039;s simpleDB</description>
		<content:encoded><![CDATA[<p>@SQL Tutorials: you could try something like Amazon&#8217;s simpleDB</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lani Rosales</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-31957</link>
		<dc:creator>Lani Rosales</dc:creator>
		<pubDate>Fri, 01 May 2009 03:49:29 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-31957</guid>
		<description>&lt;a href=&quot;http://twitter.com/webmaster_ref&quot; rel=&quot;nofollow&quot;&gt;webmaster_ref&lt;/a&gt; said on Twitter: &quot;In Perl there are other database structures that don&#039;t require any SQL, the only caveat is they don&#039;t work for big amounts of data.&quot;  Hope this helps!</description>
		<content:encoded><![CDATA[<p><a href="http://twitter.com/webmaster_ref" rel="nofollow">webmaster_ref</a> said on Twitter: &#8220;In Perl there are other database structures that don&#8217;t require any SQL, the only caveat is they don&#8217;t work for big amounts of data.&#8221;  Hope this helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL Tutorials</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-31956</link>
		<dc:creator>SQL Tutorials</dc:creator>
		<pubDate>Fri, 01 May 2009 03:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-31956</guid>
		<description>Does anyone know if there is another language or set of commands beside SQL for talking with databases? 

I&#039;m working on a project and am doing some research thanks</description>
		<content:encoded><![CDATA[<p>Does anyone know if there is another language or set of commands beside SQL for talking with databases? </p>
<p>I&#8217;m working on a project and am doing some research thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Stein</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-21935</link>
		<dc:creator>James Stein</dc:creator>
		<pubDate>Thu, 06 Nov 2008 14:45:23 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-21935</guid>
		<description>Actually it was 1984 if you want to get technical.. I was online before domain names and browsers even existed.

Unlike what most think.. The internet was not just created in 1995 or so .. The internet has existed since the early 60&#039;s, it just was not in the general public then..

Even AOL has a copyright of 1986 and eWorld (Macintosh online service) was there before AOL and as a matter fact AOL bought it out in I think it was 1994.

 James</description>
		<content:encoded><![CDATA[<p>Actually it was 1984 if you want to get technical.. I was online before domain names and browsers even existed.</p>
<p>Unlike what most think.. The internet was not just created in 1995 or so .. The internet has existed since the early 60&#8242;s, it just was not in the general public then..</p>
<p>Even AOL has a copyright of 1986 and eWorld (Macintosh online service) was there before AOL and as a matter fact AOL bought it out in I think it was 1994.</p>
<p> James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Goheen</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-21934</link>
		<dc:creator>Ben Goheen</dc:creator>
		<pubDate>Thu, 06 Nov 2008 14:35:57 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-21934</guid>
		<description>@James Stein - you&#039;ve been online since 1985?</description>
		<content:encoded><![CDATA[<p>@James Stein &#8211; you&#8217;ve been online since 1985?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Stein</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-21932</link>
		<dc:creator>James Stein</dc:creator>
		<pubDate>Thu, 06 Nov 2008 14:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-21932</guid>
		<description>I fully understand what I talk about I have been developing websites for over 15 years and I have been online for over 23 years.

 Well over 100 customers are very happy that they purchased my WP Secured solution..

 Fact is updating means nothing, the code is not encrypted and hackers have access to the code just like you do.. 

 If you change how wordpress functions then it is very obvious that hackers can not hack it as they will have no idea what changes you made.

 The past five years has seen the popularity of blogs grow in their use and as a means of making money. That&#039;s the meat that computer hackers look to sink their teeth into. A recent report by the Congressional Research Service stated that the financial impact of computer hackers amounts to $226 billion annually. Another report calculated that hackers could be taking up to six cents of every Internet dollar of revenue.

Hackers recently discovered that WordPress Blogs featured an easy path for them to cause their trouble. Many WordPress Blog owners have had their blogs hijacked in a variety of ways. They&#039;ve found ads on their WordPress Blogs that they didn&#039;t place there. Others have discovered that when someone clicks a search engine link to be taken to their WordPress Blog they&#039;re instead taken to a totally different page full of ads that are often obscene and featuring computer viruses.

 Think about it ....

 James</description>
		<content:encoded><![CDATA[<p>I fully understand what I talk about I have been developing websites for over 15 years and I have been online for over 23 years.</p>
<p> Well over 100 customers are very happy that they purchased my WP Secured solution..</p>
<p> Fact is updating means nothing, the code is not encrypted and hackers have access to the code just like you do.. </p>
<p> If you change how wordpress functions then it is very obvious that hackers can not hack it as they will have no idea what changes you made.</p>
<p> The past five years has seen the popularity of blogs grow in their use and as a means of making money. That&#8217;s the meat that computer hackers look to sink their teeth into. A recent report by the Congressional Research Service stated that the financial impact of computer hackers amounts to $226 billion annually. Another report calculated that hackers could be taking up to six cents of every Internet dollar of revenue.</p>
<p>Hackers recently discovered that WordPress Blogs featured an easy path for them to cause their trouble. Many WordPress Blog owners have had their blogs hijacked in a variety of ways. They&#8217;ve found ads on their WordPress Blogs that they didn&#8217;t place there. Others have discovered that when someone clicks a search engine link to be taken to their WordPress Blog they&#8217;re instead taken to a totally different page full of ads that are often obscene and featuring computer viruses.</p>
<p> Think about it &#8230;.</p>
<p> James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AskApache</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-21919</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Thu, 06 Nov 2008 06:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-21919</guid>
		<description>Oh and BTW, without flaming your blog..  James doesn&#039;t have a clue what he&#039;s talking about.  

Clearly lacks any knowledge/experience of auditing code to find a vulnerability, then creating a custom exploit for that vulnerability, creating an agent to carry the exploit payload across Internet Protocols recognized by the target (blog on HTTP), and finally delivering and executing the payload.  

It&#039;s quite nearly impossible to &quot;fake&quot; an IP address, read anything about IP protocols and Kevin Mitnick to get a clue.  

Updating your WP is the single best thing you can do... because exploits are custom built to exploit vulnerabilities in OLD versions.  Once an exploit is made public, through honeypots, active logging, etc.. WP releases an update.  See &quot;Open Source&quot; for basic background on how this works.

No offense James, you&#039;ve put some effort and thought into your suggestions but without understanding what an exploit is and how a server/web app/system operates you&#039;ll just be wasting your time.  

I&#039;d liken your ideas to this scenario..  A user spends a lot of time creating a custom password-login-prompt that is loaded every time a user wants to login to the admin panel. 

Seems secure.. 


[ request admin ] =&gt; [ password prompt ]


But thats completely misleading. Here&#039;s how the request really travels.

[ request admin ] ==&gt; [ protocol setup OS-dependent ] ==&gt; [ server finds requested file ] ==&gt; [ server determines how to &quot;handle&quot; file (php) ] ==&gt; [ server executes php binary or module ] ==&gt; [ php opens file according to php config ] ==&gt; [ requested file parsed by php ] ==&gt; [ php includes wp-config.php to access database ] ==&gt; [ php sends output/headers on tcp/ip connection established by server app ] ==&gt;  [ finally your password-protection is loaded and executed ]


Now that is entirely over-simplified, and you can see that there are around 15 different points in-between when the request is sent to the server and when the password-protection actually starts.  All it would take is modifying file permissions, changing wp-config.php info, modifying how the server &quot;handles&quot; php, executing a OS-level/Server-level/Protocol-level/Application-level exploit and all that so-called &quot;security&quot; is completely circumvented.</description>
		<content:encoded><![CDATA[<p>Oh and BTW, without flaming your blog..  James doesn&#8217;t have a clue what he&#8217;s talking about.  </p>
<p>Clearly lacks any knowledge/experience of auditing code to find a vulnerability, then creating a custom exploit for that vulnerability, creating an agent to carry the exploit payload across Internet Protocols recognized by the target (blog on HTTP), and finally delivering and executing the payload.  </p>
<p>It&#8217;s quite nearly impossible to &#8220;fake&#8221; an IP address, read anything about IP protocols and Kevin Mitnick to get a clue.  </p>
<p>Updating your WP is the single best thing you can do&#8230; because exploits are custom built to exploit vulnerabilities in OLD versions.  Once an exploit is made public, through honeypots, active logging, etc.. WP releases an update.  See &#8220;Open Source&#8221; for basic background on how this works.</p>
<p>No offense James, you&#8217;ve put some effort and thought into your suggestions but without understanding what an exploit is and how a server/web app/system operates you&#8217;ll just be wasting your time.  </p>
<p>I&#8217;d liken your ideas to this scenario..  A user spends a lot of time creating a custom password-login-prompt that is loaded every time a user wants to login to the admin panel. </p>
<p>Seems secure.. </p>
<p>[ request admin ] =&gt; [ password prompt ]</p>
<p>But thats completely misleading. Here&#8217;s how the request really travels.</p>
<p>[ request admin ] ==&gt; [ protocol setup OS-dependent ] ==&gt; [ server finds requested file ] ==&gt; [ server determines how to "handle" file (php) ] ==&gt; [ server executes php binary or module ] ==&gt; [ php opens file according to php config ] ==&gt; [ requested file parsed by php ] ==&gt; [ php includes wp-config.php to access database ] ==&gt; [ php sends output/headers on tcp/ip connection established by server app ] ==&gt;  [ finally your password-protection is loaded and executed ]</p>
<p>Now that is entirely over-simplified, and you can see that there are around 15 different points in-between when the request is sent to the server and when the password-protection actually starts.  All it would take is modifying file permissions, changing wp-config.php info, modifying how the server &#8220;handles&#8221; php, executing a OS-level/Server-level/Protocol-level/Application-level exploit and all that so-called &#8220;security&#8221; is completely circumvented.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AskApache</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-21918</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Thu, 06 Nov 2008 05:39:36 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-21918</guid>
		<description>Nice post Carson, 

happened to find it from a trackback I received and just now got to it in the moderation stack.  (cant find the link?).

&lt;blockquote&gt;#5 limit access to your wp-admin directory using a .htaccess file&lt;/blockquote&gt;
The AskApache Password Protection plugin tries to automate the task of securing your blog (not just wp-admin) by using .htaccess to configure your site.  You can always &lt;a href=&quot;http://wordpress.org/extend/plugins/askapache-password-protect/&quot; rel=&quot;nofollow&quot;&gt;download the plugin&lt;/a&gt; at WP, but if you are interested in the actual explanations of what the code does, check &lt;a href=&quot;http://www.askapache.com/htaccess/htaccess-plugin-blocks-spam-hackers-and-password-protects-blog.html&quot; rel=&quot;nofollow&quot;&gt;this&lt;/a&gt; post out, it shows the code.

I&#039;ve been working on the new version for a month,  so stay tuned.


The most important tips (in my experience) for keeping your blog secure that you mention above are ( 1, 4, 2, 5 )..   

If you keep WP upgraded you are safe, but keep in mind that almost all the exploits that are used to crack a WP blog are actually exploiting vulnerable PLUGINS and THEMES. 

So if you only use vetted plugins and a custom theme (delete everything else/unused) then you should be good..  Also, you mentioned using a dedicated host, and that is probably the best way to limit the potential fallout from a cracked blog from spilling over to all your other online stuff.  Nice blog!</description>
		<content:encoded><![CDATA[<p>Nice post Carson, </p>
<p>happened to find it from a trackback I received and just now got to it in the moderation stack.  (cant find the link?).</p>
<blockquote><p>#5 limit access to your wp-admin directory using a .htaccess file</p></blockquote>
<p>The AskApache Password Protection plugin tries to automate the task of securing your blog (not just wp-admin) by using .htaccess to configure your site.  You can always <a href="http://wordpress.org/extend/plugins/askapache-password-protect/" rel="nofollow">download the plugin</a> at WP, but if you are interested in the actual explanations of what the code does, check <a href="http://www.askapache.com/htaccess/htaccess-plugin-blocks-spam-hackers-and-password-protects-blog.html" rel="nofollow">this</a> post out, it shows the code.</p>
<p>I&#8217;ve been working on the new version for a month,  so stay tuned.</p>
<p>The most important tips (in my experience) for keeping your blog secure that you mention above are ( 1, 4, 2, 5 )..   </p>
<p>If you keep WP upgraded you are safe, but keep in mind that almost all the exploits that are used to crack a WP blog are actually exploiting vulnerable PLUGINS and THEMES. </p>
<p>So if you only use vetted plugins and a custom theme (delete everything else/unused) then you should be good..  Also, you mentioned using a dedicated host, and that is probably the best way to limit the potential fallout from a cracked blog from spilling over to all your other online stuff.  Nice blog!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Stein</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-21019</link>
		<dc:creator>James Stein</dc:creator>
		<pubDate>Mon, 27 Oct 2008 15:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-21019</guid>
		<description>From customers.. since you asked.. Just a few testimonials...

-----------------------
 Thanks James, just what I was looking for.

I had one of my blogs hacked a couple of weeks ago. Luckily, it was one that I hadn&#039;t spent a lot of time on so I just deleted and started it over.

It is a small price to pay to protect your business.

Again, thanks.

Lewis
-------------------

Ok well I just purchased WordPressSecured and I have to say it is detailed. I have been using WordPress for years and have read and implemented the majority of the security tips out there.

But, I have never seen anything like this. I can see that I have some work ahead of me this week updating my blogs.

James I have to say thanks for a great product that delivers what it promises.

------------------

I have to say, I&#039;ve benefited James&#039; tips on this thread pasted right below were immensely beneficial in helping me secure my WordPress:
My wordpress blog hacked - again!

Several of my WordPress sites were hacked (as well as non-WordPress scripts, a directory script, and membership scripts I paid for). Some of the hacks were truly scary like one that used one of my sites as a launch pad to send out fraudulent Bank of America emails to extract innocent victims&#039; financial information. Crap like that could land the wrong person in jail!

The most common hacks were ones based out of Turkey, who took their grievances and disputes out online on such sites as one I set up to help pets in shelters get adopted. They&#039;d deface my sites with images of soldiers, curses against Israel and Norway (what homeless dogs and ferrets have to do with these hackers&#039; grievances is beyond my understanding)

Anyway, after implementing James&#039; suggestions to secure WordPress, hackers were no longer able to penetrate my WordPress sites, though my server did report that hackers were still targeting them, sometimes slowing my sites down.

Wordpress Secure would definitely be a wise investement. I say this, having already benefited from James&#039; /The RichJerksNet expertise in this area, without having it yet. Getting it all in one resource would be very nice.</description>
		<content:encoded><![CDATA[<p>From customers.. since you asked.. Just a few testimonials&#8230;</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
 Thanks James, just what I was looking for.</p>
<p>I had one of my blogs hacked a couple of weeks ago. Luckily, it was one that I hadn&#8217;t spent a lot of time on so I just deleted and started it over.</p>
<p>It is a small price to pay to protect your business.</p>
<p>Again, thanks.</p>
<p>Lewis<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>Ok well I just purchased WordPressSecured and I have to say it is detailed. I have been using WordPress for years and have read and implemented the majority of the security tips out there.</p>
<p>But, I have never seen anything like this. I can see that I have some work ahead of me this week updating my blogs.</p>
<p>James I have to say thanks for a great product that delivers what it promises.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>I have to say, I&#8217;ve benefited James&#8217; tips on this thread pasted right below were immensely beneficial in helping me secure my WordPress:<br />
My wordpress blog hacked &#8211; again!</p>
<p>Several of my WordPress sites were hacked (as well as non-WordPress scripts, a directory script, and membership scripts I paid for). Some of the hacks were truly scary like one that used one of my sites as a launch pad to send out fraudulent Bank of America emails to extract innocent victims&#8217; financial information. Crap like that could land the wrong person in jail!</p>
<p>The most common hacks were ones based out of Turkey, who took their grievances and disputes out online on such sites as one I set up to help pets in shelters get adopted. They&#8217;d deface my sites with images of soldiers, curses against Israel and Norway (what homeless dogs and ferrets have to do with these hackers&#8217; grievances is beyond my understanding)</p>
<p>Anyway, after implementing James&#8217; suggestions to secure WordPress, hackers were no longer able to penetrate my WordPress sites, though my server did report that hackers were still targeting them, sometimes slowing my sites down.</p>
<p>WordPress Secure would definitely be a wise investement. I say this, having already benefited from James&#8217; /The RichJerksNet expertise in this area, without having it yet. Getting it all in one resource would be very nice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Stein</title>
		<link>http://agbeat.com/editorials/real-estate/hackers-attack-stats-drop-your-wordpress-blog-could-be-a-victim/#comment-21018</link>
		<dc:creator>James Stein</dc:creator>
		<pubDate>Mon, 27 Oct 2008 15:31:46 +0000</pubDate>
		<guid isPermaLink="false">http://agentgenius.com/?p=6185#comment-21018</guid>
		<description>I did not ignore them at all .. The fact that backing up and updating will not keep you safe should mean something.. This is a serious problem that has cost business income, traffic, revenue and more...

1. Rename your admin username, ok fine that does not stop hackers from accessing the admin

2. Using a dedicated server has NOTHING to do with it, even dedicated and unsecured can still be hacked.

3. Keeping up to date means nothing, the hackers also have access to these updates and remember the code is not encrypted.

4. Limit access to your admin by IP .. Any hacker can fake your IP and the fact that most have changing IP&#039;s this means nothing.. What you going to do block yourself from your own admin ?

5. Wordpress version means nothing, it still has the same coding style as older wordpress.

6. remove unused plug-ins .. I agree

7. backup.. I agree but this should be done with any site not just wordpress

 I fully read the post, fact still remains unless you take action yourself and changethe functionality of wordpress you will never ever stop the hacks. The hackers know exactly how wordpress is coded.. Unless you change how it functions, then they have no idea how to hack it as they will not have any knowledge of what you changed.

 James</description>
		<content:encoded><![CDATA[<p>I did not ignore them at all .. The fact that backing up and updating will not keep you safe should mean something.. This is a serious problem that has cost business income, traffic, revenue and more&#8230;</p>
<p>1. Rename your admin username, ok fine that does not stop hackers from accessing the admin</p>
<p>2. Using a dedicated server has NOTHING to do with it, even dedicated and unsecured can still be hacked.</p>
<p>3. Keeping up to date means nothing, the hackers also have access to these updates and remember the code is not encrypted.</p>
<p>4. Limit access to your admin by IP .. Any hacker can fake your IP and the fact that most have changing IP&#8217;s this means nothing.. What you going to do block yourself from your own admin ?</p>
<p>5. WordPress version means nothing, it still has the same coding style as older wordpress.</p>
<p>6. remove unused plug-ins .. I agree</p>
<p>7. backup.. I agree but this should be done with any site not just wordpress</p>
<p> I fully read the post, fact still remains unless you take action yourself and changethe functionality of wordpress you will never ever stop the hacks. The hackers know exactly how wordpress is coded.. Unless you change how it functions, then they have no idea how to hack it as they will not have any knowledge of what you changed.</p>
<p> James</p>
]]></content:encoded>
	</item>
</channel>
</rss>

