Softpedia
 

NEWS CATEGORIES:



NEWS ARCHIVE >>
SOFTPEDIA REVIEWS >>
MEET THE EDITORS >>
TRENDING TODAY
Home > News > Security

October 30th, 2010, 08:07 GMT · By

Linux Java-Based Trojan Might Have Been an Accident

SHARE:

Adjust text size:

Linux infection an unintended side effect of Java-based trojan
Enlarge picture
A more detailed analysis of the recently discovered cross-platform social networking trojan, suggests that the Linux infection vector might have been an unintended side effect.

The hypothesis was put forth ParetoLogic's Jerome Segura, one of the first security researchers to point out the trojan's capability of infecting Linux systems.

After analyzing the encrypted malicious code, the researcher believes that its authors only intended to target Windows and Mac OS X.

There are routines that explicitly check for Mac OS X, but none for Linux. The "might have been an accident" idea is further supported by the temporary nature of the infection on the latter.

"If they really wanted to infect Linux computers, the bad guys would have added a start-up entry to ensure the code would run each and every time the machine was started. This, by the way, is not a big deal to achieve," the researcher notes.

Symantec also published some findings that point in this direction. According to the antivirus giant, the trojan contains multiple components, one of which is used to decrypt the malicious Java classes.

However, the attack server only contained versions of this component for Windows (cplib_x86_win.klf) and Mac (cplib_x86_osx.tnw).

This doesn't change the fact that Linux users are affected, but does help explain why the infection is less effective on this OS, than on the other two.

There is also a bit of confusion about the trojan's name. While it is similar to the notorious Koobface social networking worm, ultimately, this seems to be a separate creation.

SecureMac, the company that originally reported the threat, calls it Trojan.osx.boonana.a, however, Mac antivirus vendor Intego names it OSX/Koobface.A.

Symantec also published a rundown of the infection. The company detects the malware as Trojan.Jnanabot.

"An unsuspecting user clicks on a malicious URL on a social networking site, resulting in the downloading of a dropper file.

"This file then drops and launches the main component of the threat, that is jnana.tsa, which is a .jar file. This file contains many encrypted class files.

"Cplib_x86_win [or cplib_x86_osx] module is used to encrypt and decrypt those class files. This component has the ability to control all the other components of the threat," the antivirus vendor explains.

Some people have questioned, and not without merit, the drive-by download nature of this attack. However, it's worth pointing out that, according to some theories, Java applets and ActiveX objects qualify as drive-by downloads, even though they require user interaction.


6,458 hits · 6 comments
Link to this article · Print article · Send to friend

MUST-READ RELATED ARTICLES:


New Koobface Variant Infects Linux Systems

Cross-Platform Attack Installs Trojan on Windows and Mac

Critical Patches Available for Java

Microsoft Warns of Spike in Java Exploitation Attempts

READER COMMENTS:


Comment #1 by: duke6024 on 31 Oct 2010, 15:33 UTC reply to this comment

i have i believe 7 jnana and maybe 3 vfxdsys.i believe trojan.Boonana.B i have crashes knocks out my bitdefender it is pretty good nusiance bit defender is not familar yet i have had for a month i think i also have agent AQTL quarantine they are in and not being killed they are just like there so you don't know just crash bit defender and block and send report you will have to do multiple delete type in file rar to find avg free scan didnot even notice i just don't know if i can straight up delete without taking other stuff out

Comment #1.1 by: marta80 on 15 Feb 2011, 16:05 GMT

i enjoy your article. great job. keep it simple


Comment #2 by: duke6024 on 31 Oct 2010, 16:00 UTC reply to this comment

Object Path Threat Name Final Status
File: C:\Users\User\.jnana\rvwop=>ia/plugins/facebook/FaceBookWorm.class Java.Trojan.Boonana.C Moved to Quarantine
File: C:\Users\valley\.jnana\rvwop.zip=>rvwop=>ia/plugins/facebook/FaceBookWorm.class Java.Trojan.Boonana.C Moved to Quarantine
File: C:\Users\rocky\.jnana\rvwop=>ia/plugins/facebook/FaceBookWorm.class Java.Trojan.Boonana.C Moved to Quarantine
File: C:\Users\valley\.jnana\jnana.tsa=>ia/classprotect/Start.class Java.Trojan.Boonana.B Moved to Quarantine
File: C:\Users\User\.jnana\rvwop.zip=>rvwop=>ia/plugins/facebook/FaceBookWorm.class Java.Trojan.Boonana.C Moved to Quarantine
File: C:\Users\valley\.jnana\jnana.tsa=>ia/Lake.class Java.Trojan.Boonana.B Moved to Quarantine
File: C:\Users\valley\.jnana\jnana.tsa=>ia/JPhotoAlbum.class Java.Trojan.Boonana.B Moved to Quarantine
File: C:\Users\valley\.jnana\jnana.tsa=>ia/classprotect/ClassProtect.class Java.Trojan.Boonana.B Moved to Quarantine
File: C:\Users\rocky\.jnana\rvwop.zip=>rvwop=>ia/plugins/facebook/FaceBookWorm.class Java.Trojan.Boonana.C Moved to Quarantine
File: C:\Users\rocky\.jnana\jnana.tsa=>ia/classprotect/Start.class Java.Trojan.Boonana.B Moved to Quarantine
File: C:\Users\valley\.jnana\jnana.tsa=>ia/classprotect/a.class Java.Trojan.Boonana.B Moved to Quarantine
File: C:\Users\rocky\.jnana\jnana.tsa=>ia/Lake.class Java.Trojan.Boonana.B Moved to Quarantine
File: C:\Users\rocky\.jnana\jnana.tsa=>ia/JPhotoAlbum.class Java.Trojan.Boonana.B Moved to Quarantine
File: C:\Users\rocky\.jnana\jnana.tsa=>ia/classprotect/ClassProtect.class Java.Trojan.Boonana.B Moved to Quarantine
File: C:\Users\valley\.jnana\rvwop=>ia/plugins/facebook/FaceBookWorm.class Java.Trojan.Boonana.C Moved to Quarantine
File: C:\Users\rocky\.jnana\jnana.tsa=>ia/classprotect/a.class Java.Trojan.Boonana.B Moved to Quarantine

[-]Detailed Scan Summary
[-]Basic
Scanned items: 9631
Infected items: 16
Suspect items: 0 (no suspected items have been detected)
Resolved items: 16
Unresolved items: 0 (no issues remained unresolved)

[ ]Advanced


Comment #3 by: Confused on 31 Oct 2010, 20:58 UTC reply to this comment

"added a start-up entry to ensure the code would run each and every time the machine was started. This, by the way, is not a big deal to achieve"

How is this done? I can imagine its easy to have it run when the user logs in, but to make it run when the system boots, won't the user to explicitly enter sudo password?

Comment #3.1 by: Lucian Constantin on 01 Nov 2010, 11:51 GMT

I assume he refers to "when the user logs in," which from the trojan functionality's perspective is pretty much the same as the machine starting.

Let's keep in mind that this is an attack, which uses social engineering. Therefore it targets users.

Users don't browse from servers. So, it's safe to assume that most of the affected systems would be desktops. How many people start their desktop, but don't log in?


Comment #4 by: pcrawford on 03 Jan 2011, 16:54 UTC reply to this comment

You only need to prompt for the user's sudo password if you want it machine-wide. You can infect a single account without the password, and if you goal is simple stealing user data, that is sufficient.

Copyright © 2001-2013 Softpedia. Contact/Tip us at

WindowsGamesDriversMacLinuxScriptsMobileHandheldNews

SUBMIT PROGRAM   |   ADVERTISE   |   GET HELP   |   SEND US FEEDBACK   |   RSS FEEDS   |   UPDATE YOUR SOFTWARE   |   ROMANIAN FORUM