A security researcher has posted a search tool that lets anyone sniff out malware using Google, a technique first discussed by California security vendor Websense. HD Moore, the lead developer for the Metasploit Framework open-source exploit project, created a tool and posted code that shows how to use Google to look for specific data strings — which Moore dubbed “fingerprints” — within code already defined as malicious.<\/p>\n","protected":false},"excerpt":{"rendered":"
He worked with others, including researchers at the Offensive Computing project — who gave him access to their malware database — to create the code, which includes a malware signature generator, a malware Google API signature search application, and a malware downloader.<\/p>\n
Last week, San Diego-based Websense noted that Google indexes binary files, in particular some Windows executables, and in general terms described how it created a toolset that used the search engine’s API to automate detection of malware and malicious code-infected sites on the Internet.<\/p>\n
In a July 10 interview, Dan Hubbard, Websense’s senior director of security, said the company would share the search tools only with a select group of researchers. “Rather than looking for strings within Bagle or MyDoom, look for the evidence of packers in executables.”<\/p>\n
Moore and Hubbard also disagreed on the danger of publicly releasing a Google-based malware search tool, with the latter holding to Websense’s earlier position of keeping its findings within the security community by distributing them only on private mailing lists.<\/p>\n
http:\/\/www.darkreading.com\/document.asp?doc_id=99328&WT.svl=cmpnews2_1<\/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-784","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\/784","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=784"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/784\/revisions"}],"predecessor-version":[{"id":3271,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/784\/revisions\/3271"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=784"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=784"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=784"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}