<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.thestandard.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>The Industry Standard - Google blacklists ATUG Web site - Comments</title>
 <link>http://www.thestandard.com/news/2008/10/07/google-blacklists-atug-web-site</link>
 <description>Comments for &quot;Google blacklists ATUG Web site&quot;</description>
 <language>en</language>
<item>
 <title>Google blacklists ATUG Web site</title>
 <link>http://www.thestandard.com/news/2008/10/07/google-blacklists-atug-web-site</link>
 <description>&lt;p&gt;&lt;!--paging_filter--&gt;
&lt;p&gt;Hackers may have hit the Australian Telecommunications User Group (ATUG) Web site, according to Google which has placed security threat warnings across all pages displayed in searches.&lt;/p&gt;
&lt;p&gt;The flag -- which reads &quot;this site may harm your computer&quot; -- underscores all ATUG Web pages and documents generated in Google searches. Google&#039;s badware security warning page advises users to avoid the site.&lt;/p&gt;
&lt;p&gt;ATUG was unaware of the label when contacted by Computerworld magazine Tuesday morning.&lt;/p&gt;
&lt;p&gt;The blacklists are produced by an alliance of online consumer protection groups, telcos and security vendors including AOL, VeriSign and Google, and stored in a &lt;a href=&quot;http://www.stopbadware.org/home/clearinghouse&quot; rel=&quot;nofollow&quot; rel=&quot;nofollow&quot; rel=&quot;nofollow&quot;&gt;clearinghouse&lt;/a&gt; maintained by StopBadware.org, a security watchdog used by Google to identify and evaluate malicious Web sites.&lt;/p&gt;
&lt;p&gt;Google reported malicious content on the ATUG Web site, although it refused to divulge specifics on the alert.&lt;/p&gt;
&lt;p&gt;A Google spokesperson contacted by Computerworld for a &lt;a href=&quot;http://www.techworld.com.au/index.php/id;448185739&quot; rel=&quot;nofollow&quot; rel=&quot;nofollow&quot; rel=&quot;nofollow&quot;&gt;separate article&lt;/a&gt; refused to comment on how often the company re-checks flagged Web sites; however, employee Phil Harton said in a &lt;a href=&quot;http://googlewebmastercentral.blogspot.com/2007/01/about-badware-warnings.html&quot; rel=&quot;nofollow&quot; rel=&quot;nofollow&quot; rel=&quot;nofollow&quot;&gt;blog posting&lt;/a&gt; that it can take up to two weeks to remove alerts once badware has been wiped.&lt;/p&gt;
&lt;p&gt;&quot;We&#039;ve begun sending email notifications to some of the Web masters of sites that we flag for badware. We don&#039;t have a perfect process for determining a Web master&#039;s e-mail address, so for now we&#039;re sending the notifications to likely Web master aliases for the domain in question,&quot; Harton said.&lt;/p&gt;
&lt;p&gt;The response times vary depending on the extent of infection and how quickly exploits are fixed, according to StopBadware.org.&lt;/p&gt;
&lt;p&gt;&quot;Google is the sole decider for initial decisions to post a warning page for a Web site [and it] does not rely on any testing or reports from StopBadware in making these initial decisions,&quot; the company stated on its Web site. &lt;/p&gt;
</description>
 <comments>http://www.thestandard.com/news/2008/10/07/google-blacklists-atug-web-site#comments</comments>
 <category domain="http://www.thestandard.com/taxonomy/term/1402">IDGNS</category>
 <category domain="http://www.thestandard.com/taxonomy/term/1531">Internet</category>
 <category domain="http://www.thestandard.com/taxonomy/term/1805">Intrusion</category>
 <category domain="http://www.thestandard.com/taxonomy/term/1545">Search engines</category>
 <category domain="http://www.thestandard.com/taxonomy/term/1428">Security</category>
 <category domain="http://www.thestandard.com/taxonomy/term/5667">Software &amp;amp; Web</category>
 <category domain="http://www.thestandard.com/taxonomy/term/98">Breaking News</category>
 <pubDate>Tue, 07 Oct 2008 10:46:21 -0700</pubDate>
 <dc:creator>IDG News Service</dc:creator>
 <guid isPermaLink="false">119552 at http://www.thestandard.com</guid>
</item>
</channel>
</rss>
