Linux Malware Has Been Around For Years without any detections until recently. Researchers at Qihoo 360 Network Security discovered a particularly stealthy piece of malware designed to create backdoors in the Linux ecosystem.
It was so good at its job and so stealthy that it went entirely undetected for years. That gave the hackers controlling it a convenient access point literally for years.
Based on Linux’s research, the first sample of the malware they could find of the malicious code they dubbed RotaJakiro, was uploaded in 2018. It took more than three years for anyone to become aware of the Linux Malware’s existence, and in the computer world, three years is just shy of eternity.
A Qihoo spokesman had this to say about the recent discovery of the Linux Malware:
“At the functional level, RotaJakiro first determines whether the user is root or non-root at run time, with different execution policies for other accounts, then decrypts the relevant sensitive resources using AES& ROTATE for subsequent persistence, process guarding and single instance use, and finally establishes communication with C2 and waits for the execution of commands issued by C2.
RotaJakiro supports 12 functions, three of which are related to the execution of specific Plugins. Unfortunately, we have no visibility to the plugins and therefore do not know its true purpose.”
In all, Linux’s researchers discovered four malware code samples online, all of them dating back to 2018, and no detection before Qihoo finds them.
Of interest, RotaJakiro seems to have code in common with the Torii IoT botnet. In September of 2018, Vesselin Bontchev discovers the botnet and analyzes it in depth by the Threat Intelligence Team run by Avast. Torii and RotaJakiro share many similarities to Linux Malware, including “the use of encryption algorithms to hide sensitive resources, the implementation of a rather old-school style of persistence, structured network traffic.”
In any case, Linux’s Malwareisn’t a widespread, pervasive threat, so the odds are that you’ll never actually run across it. Even so, it’s an interesting bit of code to be aware of.