<?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: GoDaddy/WordPress ninoplas Base64 virus and the fix</title>
	<atom:link href="http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/feed" rel="self" type="application/rss+xml" />
	<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix</link>
	<description>krkhan&#039;s blog</description>
	<lastBuildDate>Mon, 06 Feb 2012 18:55:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Concrete Molds ·</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-37416</link>
		<dc:creator>Concrete Molds ·</dc:creator>
		<pubDate>Mon, 08 Nov 2010 10:30:51 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-37416</guid>
		<description>godaddy is not always the best registrar, the private registration of godaddy is too expensive       -</description>
		<content:encoded><![CDATA[<p>godaddy is not always the best registrar, the private registration of godaddy is too expensive       -</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robena Eng</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-36937</link>
		<dc:creator>Robena Eng</dc:creator>
		<pubDate>Sat, 23 Oct 2010 09:17:37 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-36937</guid>
		<description>Long time viewer / first time poster. Really enjoy reading the blog, keep up the good work. Will definitely start posting more in the near future.</description>
		<content:encoded><![CDATA[<p>Long time viewer / first time poster. Really enjoy reading the blog, keep up the good work. Will definitely start posting more in the near future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-33791</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Wed, 19 May 2010 16:24:14 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-33791</guid>
		<description>i have also been victim of the ninoplas virus, but am haPpy to say i was able to remove it by doing a little searching. 

I was looking for an alternative to reinstalling all the original wordpress files, plugins, themes, etc., so i looked through a number of different files and didnt find anything until i got to the files in my themes folder. 

THE ONLY FILE THAT WAS INFECTED WAS THE HEADER.PHP FILE IN THE NAKED_HTML5 THEME. THERE WAS A LONG STRING OF CODE ADDED TO THE TOP ABOVE THE OPENING  TAG. ONCE I REMOVED THE STRING OF CODE THE PROBLEM WAS FIXED!!!</description>
		<content:encoded><![CDATA[<p>i have also been victim of the ninoplas virus, but am haPpy to say i was able to remove it by doing a little searching. </p>
<p>I was looking for an alternative to reinstalling all the original wordpress files, plugins, themes, etc., so i looked through a number of different files and didnt find anything until i got to the files in my themes folder. </p>
<p>THE ONLY FILE THAT WAS INFECTED WAS THE HEADER.PHP FILE IN THE NAKED_HTML5 THEME. THERE WAS A LONG STRING OF CODE ADDED TO THE TOP ABOVE THE OPENING  TAG. ONCE I REMOVED THE STRING OF CODE THE PROBLEM WAS FIXED!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spo</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-33788</link>
		<dc:creator>spo</dc:creator>
		<pubDate>Wed, 19 May 2010 14:46:54 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-33788</guid>
		<description>I uninstalled every copy of Wordpress that I had on my site and deleted my Wordpress database after backing it up and moving the backup off of my server, and guess what?  I STILL got hacked again.  And then I found out that I had a folder in the top level directory that was publicly writable.  I deleted that and I haven&#039;t had any problems so far.</description>
		<content:encoded><![CDATA[<p>I uninstalled every copy of WordPress that I had on my site and deleted my WordPress database after backing it up and moving the backup off of my server, and guess what?  I STILL got hacked again.  And then I found out that I had a folder in the top level directory that was publicly writable.  I deleted that and I haven&#8217;t had any problems so far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-33779</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Wed, 19 May 2010 04:43:14 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-33779</guid>
		<description>i have also been victim of the ninoplas virus, but am haPpy to say i was able to remove it by doing a little searching. 

I was looking for an alternative to reinstalling all the original wordpress files, plugins, themes, etc., so i looked through a number of different files and didnt find anything until i got to the files in my themes folder. 

THE ONLY FILE THAT WAS INFECTED WAS THE HEADER.PHP FILE IN THE NAKED_HTML5 THEME. THERE WAS A LONG STRING OF CODE ADDED TO THE TOP ABOVE THE OPENING  TAG. ONCE I REMOVED THE STRING OF CODE THE PROBLEM WAS FIXED!!!</description>
		<content:encoded><![CDATA[<p>i have also been victim of the ninoplas virus, but am haPpy to say i was able to remove it by doing a little searching. </p>
<p>I was looking for an alternative to reinstalling all the original wordpress files, plugins, themes, etc., so i looked through a number of different files and didnt find anything until i got to the files in my themes folder. </p>
<p>THE ONLY FILE THAT WAS INFECTED WAS THE HEADER.PHP FILE IN THE NAKED_HTML5 THEME. THERE WAS A LONG STRING OF CODE ADDED TO THE TOP ABOVE THE OPENING  TAG. ONCE I REMOVED THE STRING OF CODE THE PROBLEM WAS FIXED!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: serena</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-33754</link>
		<dc:creator>serena</dc:creator>
		<pubDate>Mon, 17 May 2010 12:51:21 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-33754</guid>
		<description>Hi.
I have had my godaddy website hacked with this virus 5 times in the last 3 weeks.  I am now savvy enough to backup a clean copy (at least I think its clean) every night, and as I make constant daily changes have virtually been able to pick the exact time the virus infects again and quickly grab my backup and upload straight away which seems to delete the virus from  ALL my websites infected but then it comes back within a few days.

As these websites are not WP sites as most people seem to have had problems with, can I do the SSH thing above to get rid of it or any suggestions as I can&#039;t do the restore with godaddy due to the amount of changes done during the day and any restore could have part of the malicious code on it anyway.

I manually go through and clean every .php page but wonder if I am missing something on other types of pages.

I need some layman terms in what I need to do to clean it off forever.  I have deleted any databases I had, all forum stuff everything to try not to let it come back including changing all passwords on hosting, ftp and account with godaddy

Appreciate any advice thanks
Serena</description>
		<content:encoded><![CDATA[<p>Hi.<br />
I have had my godaddy website hacked with this virus 5 times in the last 3 weeks.  I am now savvy enough to backup a clean copy (at least I think its clean) every night, and as I make constant daily changes have virtually been able to pick the exact time the virus infects again and quickly grab my backup and upload straight away which seems to delete the virus from  ALL my websites infected but then it comes back within a few days.</p>
<p>As these websites are not WP sites as most people seem to have had problems with, can I do the SSH thing above to get rid of it or any suggestions as I can&#8217;t do the restore with godaddy due to the amount of changes done during the day and any restore could have part of the malicious code on it anyway.</p>
<p>I manually go through and clean every .php page but wonder if I am missing something on other types of pages.</p>
<p>I need some layman terms in what I need to do to clean it off forever.  I have deleted any databases I had, all forum stuff everything to try not to let it come back including changing all passwords on hosting, ftp and account with godaddy</p>
<p>Appreciate any advice thanks<br />
Serena</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: carcus</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-33675</link>
		<dc:creator>carcus</dc:creator>
		<pubDate>Fri, 14 May 2010 00:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-33675</guid>
		<description>Glad I could help. Here&#039;s a tip: make it non writeable after you use it and make sure to comment out what you don&#039;t want to be run again. Our clean up script got hit and run again removing the first like of every file recursively from root. Client did not keep good backups. Use at your own risk!</description>
		<content:encoded><![CDATA[<p>Glad I could help. Here&#8217;s a tip: make it non writeable after you use it and make sure to comment out what you don&#8217;t want to be run again. Our clean up script got hit and run again removing the first like of every file recursively from root. Client did not keep good backups. Use at your own risk!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-33668</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Thu, 13 May 2010 20:21:47 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-33668</guid>
		<description>@carcus - Thanks a ton for the php script. Just used it to clean up a whole slew of infected WP sites. You&#039;re a life-saver!</description>
		<content:encoded><![CDATA[<p>@carcus &#8211; Thanks a ton for the php script. Just used it to clean up a whole slew of infected WP sites. You&#8217;re a life-saver!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: krkhan</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-33636</link>
		<dc:creator>krkhan</dc:creator>
		<pubDate>Wed, 12 May 2010 09:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-33636</guid>
		<description>@sergio: AFAIK, this JS script does nothing like that. It just redirects. We still don&#039;t know how it got there in the first place.

@carcus: Thanks for the script. Hope it helps the others.</description>
		<content:encoded><![CDATA[<p>@sergio: AFAIK, this JS script does nothing like that. It just redirects. We still don&#8217;t know how it got there in the first place.</p>
<p>@carcus: Thanks for the script. Hope it helps the others.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: carcus</title>
		<link>http://inspirated.com/2010/03/02/wordpress-ninoplas-virus-and-the-fix/comment-page-2#comment-33633</link>
		<dc:creator>carcus</dc:creator>
		<pubDate>Wed, 12 May 2010 08:10:30 +0000</pubDate>
		<guid isPermaLink="false">http://inspirated.com/?p=268#comment-33633</guid>
		<description>Here&#039;s my php code that can be run from the browser. You MUST edit this to suit your situation.

You must have safe mode off in php for it to work. Please read the comments inline.

&lt;pre lang=&quot;php&quot;&gt;
&lt;?php
//You will have to change this to your specific base64_encode
$needle=&#039;aWYoZnVuY3Rpb25fZXhpc3RzKCdvYl9zdGFydCcpJ . . . .  edit this for your specific base64_encode&#039;;

//Uncomment if you need to find your path
//$output = shell_exec(&quot;pwd&quot;);

//Uncomment to check for infected files edit the path here
//$output = shell_exec(&quot;grep -rl $needle /home/content/your/path/to/html&quot;);

//Uncomment to cleanup infected files edit hte path here
//$output = shell_exec(&quot;grep -rl $needle /home/content/your/path/to//html &#124; xargs sed -i &#039;1d&#039;&quot;);

//Output
echo &quot;$output&quot;;
?&gt;&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>Here&#8217;s my php code that can be run from the browser. You MUST edit this to suit your situation.</p>
<p>You must have safe mode off in php for it to work. Please read the comments inline.</p>

<div class="wp_syntax"><div class="code"><pre class="php" style="font-family:monospace;"><span style="color: #000000; font-weight: bold;">&lt;?php</span>
<span style="color: #666666; font-style: italic;">//You will have to change this to your specific base64_encode</span>
<span style="color: #000088;">$needle</span><span style="color: #339933;">=</span><span style="color: #0000ff;">'aWYoZnVuY3Rpb25fZXhpc3RzKCdvYl9zdGFydCcpJ . . . .  edit this for your specific base64_encode'</span><span style="color: #339933;">;</span>
&nbsp;
<span style="color: #666666; font-style: italic;">//Uncomment if you need to find your path</span>
<span style="color: #666666; font-style: italic;">//$output = shell_exec(&quot;pwd&quot;);</span>
&nbsp;
<span style="color: #666666; font-style: italic;">//Uncomment to check for infected files edit the path here</span>
<span style="color: #666666; font-style: italic;">//$output = shell_exec(&quot;grep -rl $needle /home/content/your/path/to/html&quot;);</span>
&nbsp;
<span style="color: #666666; font-style: italic;">//Uncomment to cleanup infected files edit hte path here</span>
<span style="color: #666666; font-style: italic;">//$output = shell_exec(&quot;grep -rl $needle /home/content/your/path/to//html | xargs sed -i '1d'&quot;);</span>
&nbsp;
<span style="color: #666666; font-style: italic;">//Output</span>
<span style="color: #b1b100;">echo</span> <span style="color: #0000ff;">&quot;<span style="color: #006699; font-weight: bold;">$output</span>&quot;</span><span style="color: #339933;">;</span>
<span style="color: #000000; font-weight: bold;">?&gt;</span></pre></div></div>

]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.820 seconds -->

