Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

8/9/2010
06:43 AM
Gadi Evron
Gadi Evron
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Yet Another Facebook Malware Evolution

Every once in a while I like to discuss the strategic view and how different players affect each other in the realm of cybercrime. This post is about the latest evolutionary development in the fight -- with Facebook malware.

Every once in a while I like to discuss the strategic view and how different players affect each other in the realm of cybercrime. This post is about the latest evolutionary development in the fight -- with Facebook malware.We have seen before how Facebook malware (and scams) try to lure the unsuspecting user to clicking on links, while at the same time obfuscating their activities as to not be detected by Facebook's security team.

The next phase in that evolution has happened. And much like other phases, we've seen it before in another time and place.

In 2004, botnets existed and were actively used for cybercrime activities. The security industry as a whole, save for a few individuals (including yours truly), were not aware of this threat or disregarded it as secondary.

What mattered was PR. The Year Of The Big Worms was behind us and with every new worm to be released into the wild, wilder claims would be sounded in the press, claiming the end of the world. In retrospect, while unplanned, this was as good as a campaign by the criminals to keep us in the industry busy with old technology while they make use of botnets.

Botnet was not an acknowledged term -- most of us called them Drone Armies back then. But the key issue is that these botnets performed the criminal activity a worm would, while making the shelf life of compromised computers much larger, as well as individual bots multipurpose rather than single-purpose.

And, indeed, history repeats itself, only with a different spin.

On Facebook, malware and scam activities always fight against time. They invent new tricks, and the Facebook security team responds in kind. Some of these tricks have grown to sophisticated complexity, while others are simply useless. While botnets were always used to operate fake Facebook profiles, they were not used separately for infection and scam.

In the past few weeks, we have seen more and more spam and scams on Facebook that don't actually infect the user -- thus drawing less of our attention. We keep looking for the worm, but it's not there.

What the criminals have done is divide their activities. On the one hand you have the botnet and infected users, all unrelated to Facebook. These then use Facebook on real users' computers to scam their friends. Their friends, in turn, may lose money in the scam, but will not get infected if they click the link/lure.

The difference is subtle, but key. By not infecting users on Facebook for their Facebook scams, the criminals have a lower profile and are much less interesting to Facebook security and the security industry.

In essence, the criminals, knowingly or not, have taken a page out of a security manual. They have reduced their risks by adding an extra layer, or hop, between them and their marks. Not only do they now draw less attention, it is also more difficult to discover, follow, and/or destroy these botnets because they are obfuscated behind the scenes. Don't get me wrong: Criminals have always used botnets on Facebook. This is a matter of type of usage and scale.

Ask any old timer in the industry, and he will tell you: "We've seen this before" -- in a different time, or place, or platform. This cyclical nature of our field is fascinating to me. It is always a new threat, a new platform, and a new technology. The challenge is to maintain our experience in between, and not just be tactically oriented.

Follow Gadi Evron on Twitter: http://twitter.com/gadievron.

Gadi Evron is an independent security strategist based in Israel. Special to Dark Reading. Gadi is CEO and founder of Cymmetria, a cyber deception startup and chairman of the Israeli CERT. Previously, he was vice president of cybersecurity strategy for Kaspersky Lab and led PwC's Cyber Security Center of Excellence, located in Israel. He is widely recognized for ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31769
PUBLISHED: 2021-06-21
MyQ Server in MyQ X Smart before 8.2 allows remote code execution by unprivileged users because administrative session data can be read in the %PROGRAMFILES%\MyQ\PHP\Sessions directory. The "Select server file" feature is only intended for administrators but actually does not require autho...
CVE-2020-20469
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a SQL injection vulnerability. The vulnerability stems from the log_edit.php files failing to filter the csa_to_user parameter, remote attackers can exploit the vulnerability to obtain database sensitive information.
CVE-2020-20470
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has web site physical path leakage vulnerability.
CVE-2020-20471
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has an unauthorized access vulnerability in default_user_edit.php, remote attackers can exploit this vulnerability to escalate to admin privileges.
CVE-2020-20472
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a sensitive information disclosure vulnerability. The if_get_addbook.php file does not have an authentication operation. Remote attackers can obtain username information for all users of the current site.