{"id":511,"date":"2004-01-06T00:00:00","date_gmt":"2004-01-06T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/01\/06\/microsoft-publishes-program-to-blast-msblast\/"},"modified":"2021-12-30T11:37:31","modified_gmt":"2021-12-30T11:37:31","slug":"microsoft-publishes-program-to-blast-msblast","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/01\/06\/microsoft-publishes-program-to-blast-msblast\/","title":{"rendered":"Microsoft publishes program to blast MSBlast"},"content":{"rendered":"<p>Microsoft released a removal tool for the MSBlast worm on Monday after Internet service providers complained that home users&#8217; PCs infected with the malicious program are still causing network congestion.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The MSBlast worm, also commonly called the Blaster worm, started spreading last August and is believed to have spread to hundreds of thousands of systems.<\/p>\n<p>While most corporations have cleaned up the worm, Microsoft has found that a large number of home users are still unknowingly infected, the software giant said in a statement.<br \/>\n  &#8220;For many users in this situation, there is little indication that they are infected other than possible performance degradation,&#8221; Microsoft said in a statement.  &#8220;And those infected are still actively transmitting the worm, causing Internet congestion in the process.&#8221;<\/p>\n<p>Microsoft&#8217;s aim in releasing the latest tool is to reduce the amount of traffic being born by ISPs by cleaning up a significant number of home computers.<\/p>\n<p>The tool can be found on Microsoft&#8217;s download site.<\/p>\n<p>More info: [url=http:\/\/news.com.com\/2100-1002_3-5136260.html?tag=nefd_top]http:\/\/news.com.com\/2100-1002_3-5136260.html?tag=nefd_top[\/url]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-511","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/511","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=511"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/511\/revisions"}],"predecessor-version":[{"id":2998,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/511\/revisions\/2998"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=511"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=511"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=511"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}