{"id":2306,"date":"2003-11-03T00:00:00","date_gmt":"2003-11-03T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/11\/03\/mimail-worm-variations-launch-multi-pronged-attack\/"},"modified":"2021-12-30T11:41:02","modified_gmt":"2021-12-30T11:41:02","slug":"mimail-worm-variations-launch-multi-pronged-attack","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/11\/03\/mimail-worm-variations-launch-multi-pronged-attack\/","title":{"rendered":"Mimail Worm Variations Launch Multi-Pronged Attack"},"content":{"rendered":"<p>Variants of the Mimail worm released over the weekend continued to plague businesses Monday with higher-than-usual volumes of e-mail traffic as the worm propagated by stealing addresses and mass mailing itself to new unsuspecting victims.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>All share enough characteristics, ranging from packaging their payloads in compressed .zip files to targeting specific Web sites for denial-of-service attacks, that convince analysts that one individual, or a group of attacks working together, are conducting the assault.<\/p>\n<p>To compound the problem, the variants&#8217; .zip files have been purposefully corrupted, said Dunham, so that they&#8217;re not correctly scanned by some anti-virus software.<\/p>\n<p>&#8220;The Zip files are designed to choke up some anti-virus software, making the programs give up on the scanning and move on, letting the worm through,&#8221; he noted.<\/p>\n<p>Organizations should aggressive update their anti-virus definitions, filter against the worms&#8217; known file attachments, scan compressed files,<\/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-2306","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\/2306","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=2306"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2306\/revisions"}],"predecessor-version":[{"id":4793,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2306\/revisions\/4793"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}