{"id":2333,"date":"2004-05-19T00:00:00","date_gmt":"2004-05-19T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/05\/19\/plug-and-play-port-scan-reveals-new-worms\/"},"modified":"2021-12-30T11:41:06","modified_gmt":"2021-12-30T11:41:06","slug":"plug-and-play-port-scan-reveals-new-worms","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/05\/19\/plug-and-play-port-scan-reveals-new-worms\/","title":{"rendered":"Plug and Play port scan reveals new worms"},"content":{"rendered":"<p>Investigations into recent increases in port 5000 scans have revealed the existence of two new worms: Bobax and Kibuv.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The W32\/Bobax-A worm, which employs the same Microsoft security vulnerability as the Sasser worm to break into computers, uses port 5000 to identify Windows XP systems (the port used for &#8220;Universal Plug and Play&#8221;).<\/p>\n<p>According to the Sophos Web site, this new worm &#8220;is capable of turning infected computers into spam factories and launchpads for denial-of-service attacks against Web sites.&#8221;<\/p>\n<p>The process is explained on the LURHQ security site: &#8220;unlike proxy Trojans which require the spammer to connect and send each individual piece of mail, Bobax sends the mail using a template and a list of email addresses.<\/p>\n<p>This has the benefit of offloading almost all the bandwidth requirements of spamming onto the Trojaned machines, allowing the spammer to operate with minimal cost.&#8221;<\/p>\n<p>Kibuv.B creates an FTP server on port 7955 for which any username\/password combination will work.<\/p>\n<p>Like other malware of this type, the FTP server sends a copy of the worm in response to any file request.<\/p>\n<p>The vulnerabilities exploited by these two worms are not new &#8212; users with the latest patches from Microsoft are protected.<\/p>\n<p>More info: http:\/\/news.zdnet.co.uk\/internet\/0,39020369,39155162,00.htm<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-2333","post","type-post","status-publish","format-standard","hentry","category-warnings"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2333","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=2333"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2333\/revisions"}],"predecessor-version":[{"id":4820,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2333\/revisions\/4820"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2333"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2333"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2333"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}