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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6306
Published: 2014-08-22
Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

CVE-2014-0232
Published: 2014-08-22
Multiple cross-site scripting (XSS) vulnerabilities in framework/common/webcommon/includes/messages.ftl in Apache OFBiz 11.04.01 before 11.04.05 and 12.04.01 before 12.04.04 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, which are not properly handled in a (1)...

CVE-2014-3525
Published: 2014-08-22
Unspecified vulnerability in Apache Traffic Server 4.2.1.1 and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

CVE-2014-3563
Published: 2014-08-22
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.

CVE-2014-3594
Published: 2014-08-22
Cross-site scripting (XSS) vulnerability in the Host Aggregates interface in OpenStack Dashboard (Horizon) before 2013.2.4, 2014.1 before 2014.1.2, and Juno before Juno-3 allows remote administrators to inject arbitrary web script or HTML via a new host aggregate name.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.