This page has moved to a new address.

ROAM DATA Payment Industry News Focusing on Mobile Payments

body { background:#aba; margin:0; padding:20px 10px; text-align:center; font:x-small/1.5em "Trebuchet MS",Verdana,Arial,Sans-serif; color:#333; font-size/* */:/**/small; font-size: /**/small; } /* Page Structure ----------------------------------------------- */ /* The images which help create rounded corners depend on the following widths and measurements. If you want to change these measurements, the images will also need to change. */ @media all { #content { width:740px; margin:0 auto; text-align:left; } #main { width:485px; float:left; background:#fff url("http://www.blogblog.com/rounders/corners_main_bot.gif") no-repeat left bottom; margin:15px 0 0; padding:0 0 10px; color:#000; font-size:97%; line-height:1.5em; } #main2 { float:left; width:100%; background:url("http://www.blogblog.com/rounders/corners_main_top.gif") no-repeat left top; padding:10px 0 0; } #main3 { background:url("http://www.blogblog.com/rounders/rails_main.gif") repeat-y; padding:0; } #sidebar { width:240px; float:right; margin:15px 0 0; font-size:97%; line-height:1.5em; } } @media handheld { #content { width:90%; } #main { width:100%; float:none; background:#fff; } #main2 { float:none; background:none; } #main3 { background:none; padding:0; } #sidebar { width:100%; float:none; } } /* Links ----------------------------------------------- */ a:link { color:#258; } a:visited { color:#666; } a:hover { color:#c63; } a img { border-width:0; } /* Blog Header ----------------------------------------------- */ @media all { #header { background:#456 url("http://www.blogblog.com/rounders/corners_cap_top.gif") no-repeat left top; margin:0 0 0; padding:8px 0 0; color:#fff; } #header div { background:url("http://www.blogblog.com/rounders/corners_cap_bot.gif") no-repeat left bottom; padding:0 15px 8px; } } @media handheld { #header { background:#456; } #header div { background:none; } } #blog-title { margin:0; padding:10px 30px 5px; font-size:200%; line-height:1.2em; } #blog-title a { text-decoration:none; color:#fff; } #description { margin:0; padding:5px 30px 10px; font-size:94%; line-height:1.5em; } /* Posts ----------------------------------------------- */ .date-header { margin:0 28px 0 43px; font-size:85%; line-height:2em; text-transform:uppercase; letter-spacing:.2em; color:#357; } .post { margin:.3em 0 25px; padding:0 13px; border:1px dotted #bbb; border-width:1px 0; } .post-title { margin:0; font-size:135%; line-height:1.5em; background:url("http://www.blogblog.com/rounders/icon_arrow.gif") no-repeat 10px .5em; display:block; border:1px dotted #bbb; border-width:0 1px 1px; padding:2px 14px 2px 29px; color:#333; } a.title-link, .post-title strong { text-decoration:none; display:block; } a.title-link:hover { background-color:#ded; color:#000; } .post-body { border:1px dotted #bbb; border-width:0 1px 1px; border-bottom-color:#fff; padding:10px 14px 1px 29px; } html>body .post-body { border-bottom-width:0; } .post p { margin:0 0 .75em; } p.post-footer { background:#ded; margin:0; padding:2px 14px 2px 29px; border:1px dotted #bbb; border-width:1px; border-bottom:1px solid #eee; font-size:100%; line-height:1.5em; color:#666; text-align:right; } html>body p.post-footer { border-bottom-color:transparent; } p.post-footer em { display:block; float:left; text-align:left; font-style:normal; } a.comment-link { /* IE5.0/Win doesn't apply padding to inline elements, so we hide these two declarations from it */ background/* */:/**/url("http://www.blogblog.com/rounders/icon_comment.gif") no-repeat 0 45%; padding-left:14px; } html>body a.comment-link { /* Respecified, for IE5/Mac's benefit */ background:url("http://www.blogblog.com/rounders/icon_comment.gif") no-repeat 0 45%; padding-left:14px; } .post img { margin:0 0 5px 0; padding:4px; border:1px solid #ccc; } blockquote { margin:.75em 0; border:1px dotted #ccc; border-width:1px 0; padding:5px 15px; color:#666; } .post blockquote p { margin:.5em 0; } /* Comments ----------------------------------------------- */ #comments { margin:-25px 13px 0; border:1px dotted #ccc; border-width:0 1px 1px; padding:20px 0 15px 0; } #comments h4 { margin:0 0 10px; padding:0 14px 2px 29px; border-bottom:1px dotted #ccc; font-size:120%; line-height:1.4em; color:#333; } #comments-block { margin:0 15px 0 9px; } .comment-data { background:url("http://www.blogblog.com/rounders/icon_comment.gif") no-repeat 2px .3em; margin:.5em 0; padding:0 0 0 20px; color:#666; } .comment-poster { font-weight:bold; } .comment-body { margin:0 0 1.25em; padding:0 0 0 20px; } .comment-body p { margin:0 0 .5em; } .comment-timestamp { margin:0 0 .5em; padding:0 0 .75em 20px; color:#666; } .comment-timestamp a:link { color:#666; } .deleted-comment { font-style:italic; color:gray; } .paging-control-container { float: right; margin: 0px 6px 0px 0px; font-size: 80%; } .unneeded-paging-control { visibility: hidden; } /* Profile ----------------------------------------------- */ @media all { #profile-container { background:#cdc url("http://www.blogblog.com/rounders/corners_prof_bot.gif") no-repeat left bottom; margin:0 0 15px; padding:0 0 10px; color:#345; } #profile-container h2 { background:url("http://www.blogblog.com/rounders/corners_prof_top.gif") no-repeat left top; padding:10px 15px .2em; margin:0; border-width:0; font-size:115%; line-height:1.5em; color:#234; } } @media handheld { #profile-container { background:#cdc; } #profile-container h2 { background:none; } } .profile-datablock { margin:0 15px .5em; border-top:1px dotted #aba; padding-top:8px; } .profile-img {display:inline;} .profile-img img { float:left; margin:0 10px 5px 0; border:4px solid #fff; } .profile-data strong { display:block; } #profile-container p { margin:0 15px .5em; } #profile-container .profile-textblock { clear:left; } #profile-container a { color:#258; } .profile-link a { background:url("http://www.blogblog.com/rounders/icon_profile.gif") no-repeat 0 .1em; padding-left:15px; font-weight:bold; } ul.profile-datablock { list-style-type:none; } /* Sidebar Boxes ----------------------------------------------- */ @media all { .box { background:#fff url("http://www.blogblog.com/rounders/corners_side_top.gif") no-repeat left top; margin:0 0 15px; padding:10px 0 0; color:#666; } .box2 { background:url("http://www.blogblog.com/rounders/corners_side_bot.gif") no-repeat left bottom; padding:0 13px 8px; } } @media handheld { .box { background:#fff; } .box2 { background:none; } } .sidebar-title { margin:0; padding:0 0 .2em; border-bottom:1px dotted #9b9; font-size:115%; line-height:1.5em; color:#333; } .box ul { margin:.5em 0 1.25em; padding:0 0px; list-style:none; } .box ul li { background:url("http://www.blogblog.com/rounders/icon_arrow_sm.gif") no-repeat 2px .25em; margin:0; padding:0 0 3px 16px; margin-bottom:3px; border-bottom:1px dotted #eee; line-height:1.4em; } .box p { margin:0 0 .6em; } /* Footer ----------------------------------------------- */ #footer { clear:both; margin:0; padding:15px 0 0; } @media all { #footer div { background:#456 url("http://www.blogblog.com/rounders/corners_cap_top.gif") no-repeat left top; padding:8px 0 0; color:#fff; } #footer div div { background:url("http://www.blogblog.com/rounders/corners_cap_bot.gif") no-repeat left bottom; padding:0 15px 8px; } } @media handheld { #footer div { background:#456; } #footer div div { background:none; } } #footer hr {display:none;} #footer p {margin:0;} #footer a {color:#fff;} /* Feeds ----------------------------------------------- */ #blogfeeds { } #postfeeds { padding:0 15px 0; }

Tuesday, November 2, 2010

Rogue antivirus spoofs Firefox, Google attack warning pages

» VIEW ALL POSTS Oct 20 2010   2:03PM GMT

Posted by: Robert Westervelt
Rogue Antivirus, Phishing, malicious URLs, malware

Spoofed warning page includes a download link attempting to trick users with a phony browser update.

Security researchers at F-Secure and Websense have discovered cybercriminals pitching rogue antivirus software using a spoofed version of attack warning pages used in Firefox and Google Chrome designed to block users from visiting malicious websites.

The phony attack page includes a download link that purports to be a browser update, but instead downloads rogue antivirus software, according to F-Secure.

According to F-Secure:

If your scripts are enabled, you don’t even need to click on the “Download Updates!” button. It will just offer the rogue AV to you.

It then refuses to let the user cancel the download.

In addition, Websense researchers found an iFrame that installs the Phoenix exploit kit from a different domain. Phoenix is used by cybercriminals pimping rogue AV to harvest data on infected machines and dupe the end user into buying the antivirus software. The kit consists of nine exploits for browser vulnerabilities, Java flaws, Flash errors and Adobe Reader bugs.

  Bookmark and Share            

View the original article here

Labels: , , , , , , , , ,

Rogue antivirus spoofs Firefox, Google attack warning pages

» VIEW ALL POSTS Oct 20 2010   2:03PM GMT

Posted by: Robert Westervelt
Rogue Antivirus, Phishing, malicious URLs, malware

Spoofed warning page includes a download link attempting to trick users with a phony browser update.

Security researchers at F-Secure and Websense have discovered cybercriminals pitching rogue antivirus software using a spoofed version of attack warning pages used in Firefox and Google Chrome designed to block users from visiting malicious websites.

The phony attack page includes a download link that purports to be a browser update, but instead downloads rogue antivirus software, according to F-Secure.

According to F-Secure:

If your scripts are enabled, you don’t even need to click on the “Download Updates!” button. It will just offer the rogue AV to you.

It then refuses to let the user cancel the download.

In addition, Websense researchers found an iFrame that installs the Phoenix exploit kit from a different domain. Phoenix is used by cybercriminals pimping rogue AV to harvest data on infected machines and dupe the end user into buying the antivirus software. The kit consists of nine exploits for browser vulnerabilities, Java flaws, Flash errors and Adobe Reader bugs.

  Bookmark and Share            

View the original article here

Labels: , , , , , , , , ,

Google antimalware efforts rely on website malware detection

TORONTO -- Google Inc. Tuesday revealed how it detects websites infected with malicious code, part of its effort to protect users from drive-by downloads and other malicious content.

Fabrice Jaubert of the Google antimalware team presented details about Google's antimalware efforts, Tuesday, at the SecTor 2010 conference. The team uses proprietary algorithms to identify malware distribution sites and sites that have been infected with malicious code. While Google's technical efforts succeed in identifying and blocking millions of websites suspected of hosting malicious code, Jaubert described the process as a typical cat-and-mouse game, in which savvy cybercriminals find ways to avoid detection.

"We may be better or worse [at detecting infected websites] on any given day," Jaubert said. "It's very much like the antivirus lifecycle. … We get better at detection and then the bad guys find a better hiding spot."

Jaubert said in the past 12 months, attackers have been redirecting their "infected" distribution servers to other "innocent" servers to try to avoid detection. Another problem has been the recent rise in sites peddling fake antivirus programs. Rogue antivirus programs are mutating at such a rate that Google is finding antivirus signatures unable to keep up with the changes. With antivirus signatures becoming less effective, Google is tweaking its internal algorithms in an attempt to detect and identify sites hosting fake antivirus downloads.

"Today's fake AV sites go up and down in about an hour," Jaubert said, "so it is very difficult [to stop them]."

Jaubert said Google's website malware detection pipeline begins with Internet-connected virtual machines running Windows and Internet Explorer that monitor and log all network traffic. All new processes, newly written files and registry writes are flagged, along with the infected website, and downloaded files are scanned with antivirus software. The collected information is then blended with data collected by Google's crawlers.

Despite Google's efforts, Jaubert said up to 1.5% of Google search results include a link to malware distribution sites. A substantial number of infected webpages are spam and are removed from Google's search index by a team of engineers. But webpages hosting malware typically remain in the index; if they are detected by Google's algorithm, Google uses a warning page in those search engine results.

Finding legitimate websites that contain malicious code is becoming more common, Jaubert said. "There's really no safe harbor on the net and your browsing habits are not a safe harbor in keeping you safe," he said.

Jaubert said Google is working on technical solutions to eradicate malware, but a broader approach is needed. Even if Google eradicated all sites that contained malicious code, cybercriminals would use social engineering tactics to trick users and infect their systems, he said. There's a need for a "multidisciplinary approach with a coalition of different actors" to combat the problem, he said. The United States can begin in its own backyard, he said. Twenty-five percent of malware distribution servers are located in the U.S.

"Although we do need global cooperation to address the problem fully," Jaubert said, "there are definitely servers within our reach that we can try to shut down."



View the original article here

Labels: , , , , , , ,

Google antimalware efforts rely on website malware detection

TORONTO -- Google Inc. Tuesday revealed how it detects websites infected with malicious code, part of its effort to protect users from drive-by downloads and other malicious content.

Fabrice Jaubert of the Google antimalware team presented details about Google's antimalware efforts, Tuesday, at the SecTor 2010 conference. The team uses proprietary algorithms to identify malware distribution sites and sites that have been infected with malicious code. While Google's technical efforts succeed in identifying and blocking millions of websites suspected of hosting malicious code, Jaubert described the process as a typical cat-and-mouse game, in which savvy cybercriminals find ways to avoid detection.

"We may be better or worse [at detecting infected websites] on any given day," Jaubert said. "It's very much like the antivirus lifecycle. … We get better at detection and then the bad guys find a better hiding spot."

Jaubert said in the past 12 months, attackers have been redirecting their "infected" distribution servers to other "innocent" servers to try to avoid detection. Another problem has been the recent rise in sites peddling fake antivirus programs. Rogue antivirus programs are mutating at such a rate that Google is finding antivirus signatures unable to keep up with the changes. With antivirus signatures becoming less effective, Google is tweaking its internal algorithms in an attempt to detect and identify sites hosting fake antivirus downloads.

"Today's fake AV sites go up and down in about an hour," Jaubert said, "so it is very difficult [to stop them]."

Jaubert said Google's website malware detection pipeline begins with Internet-connected virtual machines running Windows and Internet Explorer that monitor and log all network traffic. All new processes, newly written files and registry writes are flagged, along with the infected website, and downloaded files are scanned with antivirus software. The collected information is then blended with data collected by Google's crawlers.

Despite Google's efforts, Jaubert said up to 1.5% of Google search results include a link to malware distribution sites. A substantial number of infected webpages are spam and are removed from Google's search index by a team of engineers. But webpages hosting malware typically remain in the index; if they are detected by Google's algorithm, Google uses a warning page in those search engine results.

Finding legitimate websites that contain malicious code is becoming more common, Jaubert said. "There's really no safe harbor on the net and your browsing habits are not a safe harbor in keeping you safe," he said.

Jaubert said Google is working on technical solutions to eradicate malware, but a broader approach is needed. Even if Google eradicated all sites that contained malicious code, cybercriminals would use social engineering tactics to trick users and infect their systems, he said. There's a need for a "multidisciplinary approach with a coalition of different actors" to combat the problem, he said. The United States can begin in its own backyard, he said. Twenty-five percent of malware distribution servers are located in the U.S.

"Although we do need global cooperation to address the problem fully," Jaubert said, "there are definitely servers within our reach that we can try to shut down."



View the original article here

Labels: , , , , , , ,

Google extends bounty program for Web application bugs

Search giant Google Inc. Monday extended its Google bug bounty program, adding rewards for bug hunters who find serious Web application flaws in Blogger, Orkut and YouTube.

The move is an expansion of Google's current bounty program, which was launched in February to reward security researchers who reported Chrome browser flaws. Google said it would reward as much as $3,133.70 for significant flaw finds. The number pays homage to "eleet," sometimes identified as 31337, an alternative alphabet used by coders on the Internet.

"Any Google Web properties that display or manage highly sensitive authenticated user data or accounts may be in scope," Google said in an announcement on its security blog. "For now, Google's client applications (e.g. Android, Picasa, Google Desktop, etc.) are not in scope. We may expand the program in the future."

Google said it is difficult to provide a definitive list of vulnerabilities eligible for a reward, but added a number of categories that would be rewarded, including cross-site scripting errors, cross-site request forgery flaws and authorization bypass bugs. To be eligible for a reward, researchers must privately report the bugs using Google's security contact list.

"It's our job to fix serious bugs within a reasonable time frame, and we in turn request advance, private notice of any issues that are uncovered," Google said. "Vulnerabilities that are disclosed to any party other than Google, except for the purposes of resolving the vulnerability (for example, an issue affecting multiple vendors), will usually not qualify. This includes both full public disclosure and limited private release."

The base reward for qualifying bugs is $500. At each bug hunter's discretion, Google will publicly credity the finds if the flaws are deemed legitimate. Google said each submission will be evaluated by a security expert panel, which "may also decide a single report actually constitutes multiple bugs requiring reward, or that multiple reports constitute only a single reward." In addition, bug hunters can donate rewards to charity, through Google.

Google said it chose to extend the bounty program for Web application bugs because it received a sustained increase in the number of high-quality reports from researchers on bugs found in the Chromium browser, the open source browser on which Google Chrome is based. Those bugs can be reported using the Chromium bug tracker system and include flaws discovered using plug-ins shipped with the Chrome browser by default.

Some other software makers offer similar programs. Mozilla announced its Security Bug Bounty Program in 2004, funded by Linux distributor Linspire (now owned by Xandros Inc.) and Mark Shuttleworth, the founder of the Ubuntu Project. Under Mozilla's program, reporters of valid, critical security bugs nowreceive a $3,000 cash reward and a Mozilla T-shirt. The maximum cash reward was increased from $500 in July.

By contrast, Microsoft refuses to reward bug hunters with cash prizes. In an announcement in July regarding responsible disclosure, Dave Forstrom, director of Microsoft's Trustworthy Computing Program, said such programs run counter to Microsoft's vulnerability research efforts and ultimately don't help the customer.

"We don't think it's in the customer's best interest to offer a per-vulnerability bounty," Forstom said in an earlier interview. "There are a number of ways that we work with the researcher community that we think best serves the community: everything from acknowledging our work together, to all of the sponsorships of conferences that we do further develops the community."



View the original article here

Labels: , , , , ,