Vulnerabilities / Threats
6/18/2013
12:52 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

Slide Show: 10 Ways Attackers Automate Malware Production

Peeking into an attacker's toolbox to see how malware production is automated and the Internet is flooded with millions of unique malware applications
Previous
1 of 10
Next


A full field of malware creation tools has enabled attackers to transition from manually creating single-use and easily defeated malware to developing an automated production line to develop an "army of armored malware" to carry out attack campaigns, says Christopher Elisan, principal malware scientist for RSA NetWitness. Author of Malware, Rootkits & Botnets: A Beginner's Guide and a longtime malware reverser, Elisan recently offered up an extended explanation of how the process works. By using DIY malware kits like Zeus Builder, attackers with very little programming experience can create nearly infinite numbers of malware variants. From there, they can develop both protection from penetration and further variation of samples by running them through armoring tools, such as packers, crypters, and joiners. And once that process is done, they can develop automated quality assurance by running the variants through tools that lean on various AV engines to ensure that the malware remains undetected. It's a process that "basically killed AV," Elisan says and one that depends on tools like the ones outlined here.

Tool: Spy Eye

Tool Type: DIY Kit

How They're Using It: "The main idea of DIY kits is you don't need to have assembly language skills or any programming skills for that matter to create your own malware," says Elisan, who explains that these kits have actually been evolving for the better part of two decades since a 15-year-old created Virus Creation Lab (VCL) in 1992. Spy Eye is one of the first well-used kits of the modern era to use advanced features, such as encryption, and offer it in an easy GUI.

Image Credit: Christopher Elisan/RSA

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Previous
1 of 10
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.