Analytics // Threat Intelligence
8/15/2013
11:35 PM
50%
50%

Researchers Seek Better Ways To Track Malware's Family Tree

Following a program's evolution back to the author may not yet be a reality, but computer scientists are searching for more accurate measures of the relationships between software versions

Using basic features of software programs, researchers from Carnegie Mellon University have been able to organize related code into family trees, connecting initial versions to subsequent updates by using techniques that could allow malware analysts to more quickly triage unknown threats.

In a paper presented at the USENIX Security Conference this week, the three researchers -- Jiyong Jang, Maverick Woo, and David Brumley of Carnegie Mellon University -- used software features to graph the relationships between program code and track the evolution of benign and malicious software programs. The researchers created both a program, known as iLINE, to construct trees and graphs of related program versions, and a system, known as iEVAL, to evaluate the correctness of their family trees.

The researchers found that even basic measures -- such as file size and similarities among code snippets -- can be used to organize software by its lineage, from a root program to subsequent versions. Using file and section size for benign programs yielded about 95 percent accurate family trees, while using similarities in small sections of code yielded up to 96 percent.

"In the beginning, we thought constructing a lineage would be impossible," says Woo, a system scientist at Carnegie Mellon's CyLab. "But after working on it, we found that even simple techniques worked quite well."

Classifying malware into families is a necessary step for security-software firms to reduce the workload on their analysts. By creating a single signature or pattern that matches every malware variant, antivirus firms can create more efficient software and reduce their workloads.

Yet after classifying malware into a group, the next step is to determine which program should represent the family of malware, says Jiyong Jang, a co-author of the paper who just completed his PhD in electrical and computer engineering at CMU. The parent of all the programs, known as the root, is a good choice, he says.

"If you have constructed a lineage, you can determine the root and study that program," Jang says.

A major attraction of tracing the history of a malware family tree is the hope that it might lead to the root -- the developer who created the malware, says Jason Lewis, chief scientist with Lookingglass Cyber Solutions, a threat-intelligence firm

"I think the usefulness here is trying to determine who is writing the code," he says, adding that attributing code to a specific group of actors -- even if their identities are unknown -- can still be useful. "Is this someone who is interested just in stealing money and bank account information, or is this someone who is more of a state-level actor?"

[Malware writers go low-tech in their latest attempt to escape detection, waiting for human input -- a mouse click -- before running their code. See Automated Malware Analysis Under Attack.]

Attribution is typically a labor-intensive manual process. Using the automated techniques shown off by the CMU, researchers could allow malware analysts to look for complex code structures or algorithms that indicate a developer with more technical chops than the average online bank thief, Lewis says.

Yet any such analysis has to be careful not to draw too many conclusions from tenuous relationships, says Joe Stewart, director of malware research for Dell Secureworks, a managed security service provider. Two similar sets of code may not indicate a single author, but could mean that two developers collaborated, one author copied code from another, or that the two projects both used a third common library.

The researchers noted other pitfalls as well. Incorrectly guessing the root program, for example, can nearly halve the accuracy of the resulting family tree. And while the size of each section of code was a good way to match up malicious code, file size was not.

In the end, the techniques could prove useful if used to highlight interesting similarities between code so that analysts can follow up on them, Stewart says.

"You have to be careful what you infer out of [these analyses] ... but it could lead you to connections that you might not see otherwise," Stewart says. "Having something that automates the matching of software features is a good piece of the [analysis] puzzle."

Woo and Jang aim to improve their system and identify more interesting features that can be automatically extracted from program binaries, at runtime and from source code. While current methods with basic features does quite well, the aim is to create a more robust method of inferring the relationships between code and exceed 95 percent accuracy.

"We are all competing on the last 5 percent, so we need to construct more meaningful features," Woo says.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Robert Lemos is a veteran technology journalist of more than 16 years and a former research engineer, writing articles that have appeared in Business Week, CIO Magazine, CNET News.com, Computing Japan, CSO Magazine, Dark Reading, eWEEK, InfoWorld, MIT's Technology Review, ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2037
Published: 2014-11-26
Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads. NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

CVE-2014-6609
Published: 2014-11-26
The res_pjsip_pubsub module in Asterisk Open Source 12.x before 12.5.1 allows remote authenticated users to cause a denial of service (crash) via crafted headers in a SIP SUBSCRIBE request for an event package.

CVE-2014-6610
Published: 2014-11-26
Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dia...

CVE-2014-7141
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.

CVE-2014-7142
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (crash) via a crafted (1) ICMP or (2) ICMP6 packet size.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?