<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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>Kaizeku Ban &#187; vulnerability</title>
	<atom:link href="http://blog.kaizeku.com/taxonomy/vulnerability/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kaizeku.com</link>
	<description>So many evil plans, so little time...</description>
	<pubDate>Sat, 13 Dec 2008 17:01:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<meta xmlns="http://pipes.yahoo.com" name="pipes" content="noprocess" />
	<image>
		<link>http://blog.kaizeku.com/</link>
		<url>http://i.istalker.net/1.6.2/stamp.png</url>
		<title>Kaizeku Ban</title>
	</image>
		<item>
		<title>Workaround for Google Chrome Automatic file download vulnerability</title>
		<link>http://blog.kaizeku.com/ua/google-chrome/workaround-for-google-chrome-automatic-file-download-vulnerability/</link>
		<comments>http://blog.kaizeku.com/ua/google-chrome/workaround-for-google-chrome-automatic-file-download-vulnerability/#comments</comments>
		<pubDate>Thu, 18 Sep 2008 06:26:55 +0000</pubDate>
		<dc:creator>Avice</dc:creator>
		
		<category><![CDATA[Google Chrome]]></category>

		<category><![CDATA[-webkit]]></category>

		<category><![CDATA[chrome]]></category>

		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://blog.kaizeku.com/?p=241</guid>
		<description><![CDATA[Just after recent controversial privacy issue with Google Chrome browser there is old Webkit vulnerability haunting this new slick Google browser. There no official patch from the Chromium developer yet but it seem like bugs inheritance is something you should be aware of. Because Google Chrome browser is partially a Safari 3.1 with different architecture [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://blog.kaizeku.com/wp-content/uploads/2008/09/google-chrome-pokeball-simonoffice3.jpg" alt="google chrome carpet bombing-download vulnerability" title="google-chrome-pokeball-simonoffice3" width="276" height="67" class="alignright size-full wp-image-245" />Just after recent <a href="http://www.eff.org/deeplinks/2008/09/google-cuts-server-log-retention-nine-months">controversial privacy issue</a> with <strong><a href="http://www.google.com/chrome" title="Google Chrome">Google Chrome</a></strong> browser there is old <a href="http://en.wikipedia.org/wiki/WebKit" title="Wikipedia Webkit">Webkit</a> vulnerability haunting this new slick Google browser. There no official patch from the Chromium developer yet but it seem like bugs inheritance is something you should <em>be aware</em> of. Because Google Chrome browser is partially a Safari 3.1 with different architecture without JavascriptCore (script parse with <a href="http://code.google.com/p/v8/" title="Google Chrome open source javascript V8 Engine">Google open source javascript V8 Engine</a>).</p>
<p>Current Chrome (beta) is based on <strong>WebKit 525.13</strong> (Safari 3.1) rendering engine and introduces many of features inspired/taken from different modern browser (including some <a href="http://support.apple.com/kb/HT1315" title="safari 3.1 vulnerabilities">vulnerabilities</a>). Theoretically any previous vulnerability in AppleWebkit/Safari 3.1 is shared by Chrome users.</p>
<p><span id="more-241"></span>
<p><img src="http://blog.kaizeku.com/wp-content/uploads/2008/09/google-chrome-webkit-52513.jpg" alt="Google Chrome WebKit 525.13 / Safari 3.1" title="google-chrome-webkit-52513" width="420" height="200" class="aligncenter size-full wp-image-242" /></p>
<h3>Workaround for Google Chrome Carpet Bombing vulnerability</h3>
<p>As expected from previous Safari ticket on this vulnerabilty, both Safari &#038; Chrome developer label this as non vulnerability threat so there no fixes/patch (aka WontFix) for this particular issue. Blame it on interface design.<img src="http://blog.kaizeku.com/wp-content/uploads/2008/09/google-chrome-issue-867-carpet-bombing.jpg" alt="Automatic file download without confirmation possible" title="google-chrome-issue-867-carpet-bombing" width="400" height="205" class="alignnone size-full wp-image-244 mgt" /> </p>
<p>The below guide is simple workaround for Chrome <a href="http://www.oreillynet.com/onlamp/blog/2008/05/safari_carpet_bomb.html">Carpet Bombing</a> vulnerability (<a href="http://code.google.com/p/chromium/issues/detail?id=897" title="Automatic file download without confirmation possible">#897 : Automatic file download without confirmation possible</a>) . Basically just disabled the auto save file to desktop by default.</p>
<ol class="xoxo mgb">
<li>Click on the &#8220;Tools wrench icon&#8221; <img src="http://blog.kaizeku.com/wp-content/uploads/2008/09/google-chrome-toolsmenu.gif" alt="google-chrome-toolsmenu" title="google-chrome-toolsmenu" width="43" height="34" class="alignnone size-full wp-image-243" />and select <span class="fw">Options</span>.</li>
<li>On the <em>Options windows </em>select the <span class="fw">&#8220;Minor Tweaks&#8221;</span> tab.</li>
<li>Then checked the <em class="hilite-2">&#8220;Ask where to save each file before downloading&#8221;</em> check box.</li>
<li> Close the options windows. end </li>
</ol>
<p>Chromium team should enabled the above options by default. That would prevent malicious attack. It&#8217;s not very exciting to see all of this happening within short time periods.</p>
<h3 class="mgt">Related External Links</h3>
<ul class="xoxo">
<li><a href="http://code.google.com/chromium/" title="Google Code Chromium">Google Code Chromium</a></li>
<li><a href="http://groups.google.com/group/google-chrome-help" title="Google Chrome Help Discussion Group">Google Chrome Discussion Group</a></li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://blog.kaizeku.com/ua/google-chrome/workaround-for-google-chrome-automatic-file-download-vulnerability/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Wordpress &#34;Press This&#34; Multiple XSS Vulnerability</title>
		<link>http://blog.kaizeku.com/wordpress/wordpress-26-press-this-multiple-xss-vulnerability/</link>
		<comments>http://blog.kaizeku.com/wordpress/wordpress-26-press-this-multiple-xss-vulnerability/#comments</comments>
		<pubDate>Fri, 01 Aug 2008 03:16:18 +0000</pubDate>
		<dc:creator>Avice</dc:creator>
		
		<category><![CDATA[WordPress]]></category>

		<category><![CDATA[2.6]]></category>

		<category><![CDATA[security]]></category>

		<category><![CDATA[vulnerability]]></category>

		<category><![CDATA[xss]]></category>

		<guid isPermaLink="false">http://blog.kaizeku.com/?p=219</guid>
		<description><![CDATA[WordPress Press this (WP 2.6) features is exposed to multiple cross-site scripting issues because it fails to sufficiently sanitize user-supplied input. The issue can be found at Wordpress trac #7220
POC
*/wp-admin/press-this.php/?ajax=video&#038;s=%3C/textarea%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E
*/wp-admin/press-this.php/?ajax=thickbox&#038;i=%22%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E
Patch
the latest patch #8320 (07/09/08 19:51:53) by Ryan]]></description>
			<content:encoded><![CDATA[<p><img src="http://blog.kaizeku.com/wp-content/uploads/2008/08/wordpress-press-this-xss-vulnerability-pinpreview-by-chaoskaizer.png" alt="XSS Vulnerability" title="Wordpress &#34;Press This&#34; Multiple XSS Vulnerability" width="128" height="128" class="alignleft size-full wp-image-220" />WordPress <strong><a href="http://codex.wordpress.org/index.php?title=Press_This">Press this</a></strong> (WP 2.6) features is exposed to multiple cross-site scripting issues because it fails to sufficiently sanitize user-supplied input. The issue can be found at Wordpress trac <a href="http://trac.wordpress.org/ticket/7220">#7220</a></p>
<h2 title="Proof of Concept">POC</h2>
<pre class="prebox">*/wp-admin/press-this.php/?ajax=video&#038;s=%3C/textarea%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E
*/wp-admin/press-this.php/?ajax=thickbox&#038;i=%22%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E</pre>
<h3 class="mgt">Patch</h3>
<p>the latest patch <a href="http://trac.wordpress.org/changeset/8302">#8320</a> <small>(07/09/08 19:51:53)</small> by Ryan</p>]]></content:encoded>
			<wfw:commentRss>http://blog.kaizeku.com/wordpress/wordpress-26-press-this-multiple-xss-vulnerability/feed/</wfw:commentRss>
		</item>
		<item>
		<title>goro spam injection patch</title>
		<link>http://blog.kaizeku.com/wordpress/goro-spam-injection-wp-head-patch/</link>
		<comments>http://blog.kaizeku.com/wordpress/goro-spam-injection-wp-head-patch/#comments</comments>
		<pubDate>Sat, 14 Jun 2008 18:58:51 +0000</pubDate>
		<dc:creator>Avice</dc:creator>
		
		<category><![CDATA[Black Hat]]></category>

		<category><![CDATA[WordPress]]></category>

		<category><![CDATA[plugins]]></category>

		<category><![CDATA[blackhat]]></category>

		<category><![CDATA[goro]]></category>

		<category><![CDATA[injection]]></category>

		<category><![CDATA[lambda-style]]></category>

		<category><![CDATA[Owned]]></category>

		<category><![CDATA[parasite host]]></category>

		<category><![CDATA[security]]></category>

		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://blog.kaizeku.com/?p=168</guid>
		<description><![CDATA[wordpress goro spam injection patch]]></description>
			<content:encoded><![CDATA[<p><img src="http://blog.kaizeku.com/wp-content/uploads/2008/06/hacked.png" alt="goro spam injection" title="goro spam injection" width="128" height="128" class="fl size-full thumb- wp-image-169" longdesc="http://blog.kaizeku.com/wp-content/uploads/2008/06/hacked.png" />Since early 2007 I been monitoring this <a href="http://blog.kakkoi.net/wordpress/how-to-removed-wordpress-net-in-spam-injection-infected-by-mike-jagger-goro-class-mailphp/" rel="external" rev="vote-for" title="WordPress spam injection">famous WordPress spam injection</a> that only target high PR wordpress blogs like Al gore, blake ross, bluehost CEO to name a few. </p>
<h2>PHP create_function&#40;&#41;</h2>
<p>The new variant from <tt>wordpress.net.in</tt> &amp; <tt>qwetro.com</tt> used the &#8220;anonymous PHP <tt><a href="http://my2.php.net/manual/en/function.create-function.php" title="PHP manual for create_function" rel="external">create_function</a></tt>&#8221; to append their spam links on their victim blog. Below is quick patch to disabled the mischievous &#8220;create_function&#8221; injection on wp_head.</p>
<p>The below code will look for &#8220;<tt>&#65533;lambda_n</tt>&#8221; function inside <em>wp_head</em> wp_filters array and remove the action hook silently. I assume that any sane developer will never used this unstable PHP function.</p>
<pre class="prebox" style="height:830px">&#47;&#42;&#42;
 &#42; Remove create_function action hook
 &#42; append on wordpress wp_head filters
 &#42;
 &#42; &#64;author Avice De&#39;v&#233;reux &#60;ck&#64;kaizeku&#46;com&#62;
 &#42; &#64;copyright Copyright &#40;c&#41; 2006 Avice De&#39;v&#233;reux
 &#42; &#64;version 1&#46;0
 &#42; &#64;license http&#58;&#47;&#47;www&#46;gnu&#46;org&#47;licenses&#47;lgpl&#46;html GNU Lesser General Public License
 &#42; &#64;link http&#58;&#47;&#47;blog&#46;kaizeku&#46;com&#47;wordpress&#47;goro&#45;spam&#45;injection&#45;wp&#45;head&#45;patch&#47;
 &#42;&#47;
function remove_create_function_action&#40;&#41;
&#123; global &#36;wp_filter&#59;

	&#36;action_ref	&#61; &#39;wp_head&#39;&#59;
	&#36;filter 	&#61; &#36;wp_filter&#91;&#36;action_ref&#93;&#59;
	&#36;_lambda	&#61; array&#40;&#41;&#59;

	foreach&#40;range&#40;1&#44;10&#41; as &#36;priority&#41;&#123;

		if &#40;isset&#40;&#36;filter&#91;&#36;priority&#93;&#41;&#41;
		&#123;
			foreach&#40;&#36;filter&#91;&#36;priority&#93; as &#36;registered_filter &#41;&#123;

				&#36;callback &#61; &#40;string&#41; &#36;registered_filter&#91;&#39;function&#39;&#93;&#59;

				if &#40; preg_match&#40;&#34;&#47;lambda&#47;&#34;&#44; &#36;callback&#41; &#41; &#123;
		 	 		&#36;_lambda&#91;&#36;priority&#93;&#91;&#93; &#61; &#36;callback&#59;
				&#125;
			&#125;

		&#125;
	&#125;

	if &#40; count&#40;&#36;_lambda&#41; &#62;&#61; 0 &#41;&#123;

		foreach&#40;&#36;_lambda as &#36;priority &#61;&#62; &#36;callback&#41; &#123;
			if &#40; has_filter&#40;&#36;action_ref&#44;&#36;callback&#41; &#41;&#123;
				remove_filter&#40;&#36;action_ref&#44; &#36;callback&#44; &#36;priority&#44; 1&#41;&#59;
			&#125;
		&#125;
	&#125;
&#125;

add_action&#40;&#39;init&#39;&#44;&#39;remove_create_function_action&#39;&#41;&#59;
</pre>
<p><span id="more-168"></span></p>
<p class="sticky">note: This method only disabled the spam link from showing on your <span class="fw">blog header</span>. it wont fixed your blog vulnerabilities. your blog still owned thought. Tips &rarr; <a href="http://wordpress.org/download/" title="WordPress download archive" rel="external">http://wordpress.org/download/</a></p>
<h3>Download</h3>
<ul class="xoxo">
<li>Note: There is a file embedded within this post, please visit this post to download the file.</li>
</ul>
<h5 class="mgt">Related Articles</h5>
<ul class="xoxo">
<li><a href="http://blog.kakkoi.net/wordpress/how-to-removed-wordpress-net-in-spam-injection-infected-by-mike-jagger-goro-class-mailphp/" rel="external" title="Fixes wordpress.net.in Spam">Fixes wordpress.net.in Spam Footer Injection</a></li>
<li><a href="http://robertogaloppini.net/2007/12/12/wordpress-spam-injection-goro-hacked-my-blog/" rel="external" title="Roberto Galoppini">Roberto Galoppini&#8217;s, Wordpress Spam Injection: ‘Goro’ hacked my blog</a></li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://blog.kaizeku.com/wordpress/goro-spam-injection-wp-head-patch/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Co-Founder of Mozilla Project</title>
		<link>http://blog.kaizeku.com/wordpress/blake-ross-hacked-wordpress-blackhat-spammer/</link>
		<comments>http://blog.kaizeku.com/wordpress/blake-ross-hacked-wordpress-blackhat-spammer/#comments</comments>
		<pubDate>Thu, 28 Feb 2008 19:46:07 +0000</pubDate>
		<dc:creator>Avice</dc:creator>
		
		<category><![CDATA[Black Hat]]></category>

		<category><![CDATA[Owned]]></category>

		<category><![CDATA[WordPress]]></category>

		<category><![CDATA[blackhat]]></category>

		<category><![CDATA[blake ross]]></category>

		<category><![CDATA[gehackt]]></category>

		<category><![CDATA[goro]]></category>

		<category><![CDATA[mozilla]]></category>

		<category><![CDATA[parasite hosting]]></category>

		<category><![CDATA[vulnerability]]></category>

		<category><![CDATA[xmlrpc]]></category>

		<guid isPermaLink="false">http://blog.kaizeku.com/wordpress/blake-ross-hacked-wordpress-blackhat-spammer/</guid>
		<description><![CDATA[Blake Ross, the Co-Founder of Mozilla Project WordPress Blog&apos;s Hacked by Wordpress.net.in Blackhat Spammer.]]></description>
			<content:encoded><![CDATA[<p><span class="vcard"><img src='http://blog.kaizeku.com/wp-content/uploads/2008/03/blakeross-com-hack-by-blackhat.png' alt='blakeross-com-hack-by-blackhat.png' width='128' height='128' class="photo thumb- fl" longdesc='http://blog.kaizeku.com/wordpress/blake-ross-hacked-wordpress-blackhat-spammer/' /><a class="url fn microformat icn-r1" href="http://blakeross.com"><span class="given-name dc-name">Blake</span> <span class="family-name surname">Ross</span></a></span> WordPress blog is being run by <strong class="fw-">wordpress.net.in</strong> <a href="http://blog.kakkoi.net/wordpress/mattheaton-bluehost-hostmonster-ceo-hacked/" class="exturl icn-r1">goro spam</a> injection.</p>
<h3>Who&apos;s Blake Ross</h3>
<p class="mgb-"><small>Excerpt from <a class="exturl icn-r1" href="http://en.wikipedia.org/wiki/Blake_Ross">wikipedia</a></small></p>
<blockquote class="mgt-"><p class="cite"><strong>Blake Aaron Ross</strong> is a software developer who is known for his work on the Mozilla web browser; in particular, he started the Mozilla Firefox project with Dave Hyatt, as well as the Spread Firefox project with Asa Dotzler while working as a contractor at the Mozilla Foundation.<span class="db">In 2005, he was nominated for Wired magazine&#8217;s top Rave Award, Renegade of the Year, opposite Larry Page, Sergey Brin and Jon Stewart. He was also a part of Rolling Stone magazine&#8217;s 2005 hot list.</span></p>
</blockquote>
<p><span id="more-128"></span><br />
<small class="rgb-hgray"><a href="http://en.wikipedia.org/wiki/Image:Blake_Ross_WIRED_cover.jpeg" class="exturl icn-r1">Image Source</a>, The cover for issue #13.02 (the February 2005 edition) of Wired magazine featuring Blake Ross holding a Firefox globe as part of the lead article, The Firefox Explosion, about the browser&#8217;s development history.</small></p>
<h3 class="cb mgb- mgt">HTML Source &#038; ScreenGrab</h3>
<ul class="xoxo exturl pdt">
<li><a class="inturl" type="text/plain" rel="nofollow robots-nofollow noarchive" title="blakeross.com wordpress 2.0.4 html sources text" href='http://blog.kaizeku.com/wp-content/uploads/2008/02/blakeross-com-022808source.txt' title='blakeross-com-022808source.txt' rev="site:upload-txt">blakeross-com-022808-source.txt</a></li>
<li><a href="http://chaos-kaizer.deviantart.com/art/blakeross-com-hacked-78643257">Screenshot taken on Feb 28th, 2008</a></li>
</ul>
<h2 class="mgt">WordPress Vulnerability</h2>
<ol class="xoxo">
<li>
<h4 class="mgb-">Outdated WordPress</h4>
<ul class="exturl">
<li>
<h4 class="title-">WordPress 2.0.4 Exploit &amp; Vulnerability</h4>
<ul>
<li>Blake&#8217;s is running on <a href="http://wordpress.org/development/2006/07/wordpress-204/" class="exturl icn-r1" title="WordPress Development Blog &raquo; WordPress 2.0.4 Security Release">WordPress 2.0.4</a> first release on Jul 29th, 2006.</li>
<li><a href="http://trac.wordpress.org/browser/branches/2.0/wp-content/plugins/wp-db-backup.php?rev=4226">wp-db-backup.php</a> directory traversal <a href="http://trac.wordpress.org/changeset/4226" class="exturl icn-r1">Rev.4226</a></li>
<li><a href="http://markjaquith.wordpress.com/2006/10/17/changes-in-wordpress-205/">Mark Jaquith on WordPress 2.0.5 Changelog</a></li>
</ul>
</li>
<li>&#181; <small title="Proxy Cached on Feb 28th 2008 via d95.com">Proxy Cached:</small> <a rel="nofollow robots-nofollow noarchive" href="/uri/ZDk1LmNvbS8yNDAx.curie,80,302" title="redirect to blakeross.com wordpress feed">blakeross.com WordPress Version (feed)</a></li>
</ul>
</li>
<li class="mgt">
<h3 class="mgb-">WordPress Core Directory &amp; Plugins Informations Leak</h3>
<ul class="exturl">
<li>
<h3 class="title-">View blakeross.com WordPress Core Directory Listing</h3>
<pre class="prebox dn">
Index of /wp-includes

 Name Last modified Size Description

[DIR] Parent Directory 25-Dec-2006 01:14 -
[ ] cache.php 03-Sep-2006 23:52 11k
[ ] capabilities.php 03-Sep-2006 23:52 11k
[ ] class-IXR.php 03-Sep-2006 23:52 27k
[ ] class-pop3.php 03-Sep-2006 23:52 21k
[ ] class-snoopy.php 03-Sep-2006 23:52 37k
[ ] classes.php 03-Sep-2006 23:52 51k
[ ] comment-functions.php 03-Sep-2006 23:52 31k
[ ] default-filters.php 03-Sep-2006 23:52 5k
[ ] feed-functions.php 03-Sep-2006 23:52 4k
[ ] functions-compat.php 03-Sep-2006 23:52 3k
[ ] functions-formatting..> 03-Sep-2006 23:53 34k
[ ] functions-post.php 03-Sep-2006 23:53 30k
[ ] functions.php 03-Sep-2006 23:53 71k
[ ] gettext.php 03-Sep-2006 23:53 11k
[DIR] images/ 03-Sep-2006 23:50 -
[DIR] js/ 03-Sep-2006 23:55 -
[ ] kses.php 03-Sep-2006 23:55 22k
[ ] links.php 03-Sep-2006 23:55 20k
[ ] locale.php 03-Sep-2006 23:55 3k
[ ] pluggable-functions.php 03-Sep-2006 23:55 17k
[ ] registration-functio..> 03-Sep-2006 23:55 4k
[ ] rss-functions.php 03-Sep-2006 23:55 21k
[ ] streams.php 03-Sep-2006 23:55 4k
[ ] template-functions-a..> 03-Sep-2006 23:55 5k
[ ] template-functions-c..> 03-Sep-2006 23:56 13k
[ ] template-functions-g..> 03-Sep-2006 23:56 21k
[ ] template-functions-l..> 03-Sep-2006 23:56 15k
[ ] template-functions-p..> 03-Sep-2006 23:56 15k
[ ] template-loader.php 03-Sep-2006 23:56 2k
[ ] vars.php 03-Sep-2006 23:56 3k
[ ] version.php 03-Sep-2006 23:56 1k
[ ] wp-db.php 03-Sep-2006 23:56 10k
[ ] wp-l10n.php 03-Sep-2006 23:56 2k 

Apache/1.3.39 Server at blakeross.com Port 80
</pre>
<p>&#181; <small title="Proxy Cached on Feb 28th 2008 via d95.com">Proxy Cached:</small> <a rel="nofollow robots-nofollow noarchive" href="/uri/ZDk1LmNvbS9mNGEx.curie,80,302" rev="site:redirect" title="redirect to blakeross.com wordpress core directory">http://blakeross.com/wp-includes/</a></li>
<li>
<h3 class="title-">View blakeross.com WordPress Plugins Directory Listing</h3>
<pre class="prebox dn">
Index of /wp-content/plugins

 Name Last modified Size Description

[DIR] Parent Directory 27-Sep-2006 22:27 -
[DIR] akismet/ 03-Sep-2006 23:52 -
[ ] hello.php 03-Sep-2006 23:52 2k
[ ] wp-db-backup.php 03-Sep-2006 23:52 30k 

Apache/1.3.39 Server at blakeross.com Port 80
</pre>
<p>&#181; <small title="Proxy Cached on Feb 28th 2008 via d95.com">Proxy Cached:</small> <a rel="nofollow robots-nofollow noarchive" href="/uri/ZDk1LmNvbS81NmQ3.curie,80,302" title="redirect to blakeross.com wordpress plugins directory">http://blakeross.com/wp-content/plugins</a>
</li>
</ul>
</li>
</ol>
<h3>Hardening Wordpress?</h3>
<p>There is <a class="google icn-l" href="http://www.google.com/search?hl=en&amp;q=%E2%80%9Cparent+directory%E2%80%9D+wp-content%2Fplugins%2F+-text+%E2%80%93php+-shtml+-md5+-md5sums">105,000 WordPress blogs</a> leaking their plugins informations for BotNet to scan.</p>
<h2>Blackhat SEO targeting High PR WordPress Blog</h2>
<p><strong class="fw-">Blake Ross</strong> is not alone, there is similar <abbr title="Parasite Host">Spamride</abbr> cases for the past few months. Below is are few &#8220;High PR WordPress Blogs&#8221; with similar issues.</p>
<h3 class="mgb-">Others Popular Victim</h3>
<ul class="xoxo exturl">
<li><a href="http://www.climatecrisis.net/blog/" title="Al Gore&apos;s Blog"> Al Gore&#8217;s Blog</a></li>
<li><a href="http://mattheaton.com">Bluehost Hostmonster CEO&#8217;s Blog</a></li>
<li>blog.indeed.com</li>
<li>thinkingphp.org</li>
<li>floaridablog.org</li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://blog.kaizeku.com/wordpress/blake-ross-hacked-wordpress-blackhat-spammer/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
