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, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2006-1318
Published: 2014-09-19
Microsoft Office 2003 SP1 and SP2, Office XP SP3, Office 2000 SP3, Office 2004 for Mac, and Office X for Mac do not properly parse record lengths, which allows remote attackers to execute arbitrary code via a malformed control in an Office document, aka "Microsoft Office Control Vulnerability."

CVE-2014-1391
Published: 2014-09-19
QT Media Foundation in Apple OS X before 10.9.5 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted movie file with RLE encoding.

CVE-2014-4350
Published: 2014-09-19
Buffer overflow in QT Media Foundation in Apple OS X before 10.9.5 allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted MIDI file.

CVE-2014-4376
Published: 2014-09-19
IOKit in IOAcceleratorFamily in Apple OS X before 10.9.5 allows attackers to execute arbitrary code in a privileged context or cause a denial of service (NULL pointer dereference) via an application that provides crafted API arguments.

CVE-2014-4390
Published: 2014-09-19
Bluetooth in Apple OS X before 10.9.5 does not properly validate API calls, which allows attackers to execute arbitrary code in a privileged context via a crafted application.

Best of the Web
Dark Reading Radio