Malware experts from Kaspersky Lab have asked the programming community for help identifying the programming language, compiler or framework that was used to write an important part of the Duqu Trojan, in the hope that it could reveal clues about who created it or why.
“When we checked Duqu it looked totally unknown and that was very curious, because it’s unclear why something very custom was developed and used,” said Vitaly Kamluk, chief malware expert with Kaspersky Lab’s global research & analysis team.
Understanding how a piece of malware was created can offer clues about where to look for it next or the level of resources required for its development, the security expert said.
Some parts of the Duqu payload DLL, the component responsible for interacting with the command and control servers, downloading and executing additional modules, and performing other tasks, were written in standard C++, but a big chunk of it was not.
“This slice is different from others, because it was not compiled from C++ sources. It contains no references to any standard or user-written C++ functions, but is definitely object-oriented,” said Kaspersky Lab expert Igor Soumenkov in a blog post that describes the particularities of the unfamiliar code.
Kaspersky researchers refer to this portion of the Trojan as “The Duqu Framework” and believe that it might have been created by a different programming team. The unusual code is also particular to Duqu and doesn’t exist in Stuxnet, unlike some other parts that were directly borrowed from the infamous industrial sabotage malware.
“The mysterious programming language is definitively NOT C++, Objective C, Java, Python, Ada, Lua and many other languages we have checked,” Soumenkov said, adding that Kaspersky’s research team has spent countless hours analyzing the code.
The company’s researchers even discussed it with third-party experts, but didn’t get any closer to solving the mystery. “It looks absolutely alien,” Kamluk said.
Finally, Kaspersky Lab appealed to the entire programming community in the hope that someone might recognize the code constructions and figure out what was framework, toolkit or language was used.
The company has received various suggestions in comments on its blog, that range from F, D, Iron Python, High-Level Assembly, Common LISP, Forth, Erlang, Vala, to more exotic tools like RoseRT, which one user claims was used in secure government projects.
“It took us several weeks to check commonly used programming languages and various compilers,” Kamluk said. “So, I guess it may also take some time to check other suggestions.”