Author: John Scott-Railton
The Citizen Lab developed the original design of Psiphon, a censorship circumvention software, which was spun out of the lab into a private Canadian corporation (Psiphon Inc.) in 2008. In the past 24 hours, we have identified a malicious repackaging of the Psiphon 3 circumvention tool. The malware contains both a functioning copy of Psiphon, and the njRAT trojan. When executed, the implant communicates with a Syrian Command and Control server. This is likely part of a targeted attack against the Syrian opposition by a known actor, not all users of Psiphon.
Interestingly, this is not the first time we identified a malicious repackaging of circumvention programs in the context of the Syrian conflict. For example, in June 2013 we published a report describing how attackers had maliciously modified the proxy software Freegate.
This brief note describes the implant’s appearance and behavior, then explains how to obtain and verify genuine copies of Psiphon 3. The Psiphon team is monitoring the attack, and Karl Kathuria (Psiphon’s VP) encourages all new users of Psiphon to check the validity of their client. If in doubt, visit psiphon.ca to download a new copy.
Details and Appearance of the Malware
The file name and icon are intended to appear identical to a genuine Psiphon 3 executable file. The malware is believed to be part of an active campaign.
The malware was first observed on the night of 11 March 2014 (Pacific Time): Virus Total has the binary with detection of 3/50 at time of writing.
Examination of the properties of a malicious and genuine Psiphon 3 provides the first clue that the file may not be what it seems. The malicious packaging is unsigned, whereas Psiphon 3 is always signed.
The file appears to have been written in Visual Studio, and the PE is .NET dependent. Examination of strings in the binary indicate limited operational security (or deliberate misinformation) on the part of the attackers.
Infection & Persistence
Once executed, the user sees the Psiphon 3 GUI. The malware has, in fact, dropped and executed a working copy of Psiphon 3 alongside the implant.
A malicious file is dropped by psiphon.exe into the User’s AppData\Local folder:
Psiphon 3 is dropped and run from the same directory:
Meanwhile, Tempserver.exe makes the infection permanent by adding a copy of itself to the Windows Startup folder named “chrome.exe.”
Tempserver.exe also copies itself as explorer.exe, and executes the newly created PE implant.
This file is, in fact, the trojan njRAT.
Some Other Behavior
The implant, explorer.exe, begins collecting keystrokes, and writing the output to a file in the directory it was created in.
Here we see the keylogger capturing credentials as the victim enters credentials into Gmail.com via Internet Explorer and writing them to Explorer.exe.tmp.
Interestingly, the keylogger records “TAB” as “TAP,” a behavior that may help in identification.
Among other activities, the implant modifies the Windows Firewall to allow itself access to the network by issuing the following command line to netsh.exe
Command & Control
The implant initiates a TCP connection with 18.104.22.168 from port 49189 to the C2 on port 1960. Whois records for this IP address indicate that it is in Syria.
Psiphon 3 is a widely used and trusted circumvention product. It is unsurprising that it, along with other security and communications tools used by Syrian opposition groups, should be maliciously re-purposed. We do not believe this indicates a broader attack against Psiphon 3 users throughout the globe. Instead we suspect this was developed for yet another targeted attack against the opposition. Similarly, njRAT has been widely used by attackers in Syria, and is frequently packaged with dummy or functional programs. The continued targeting of security and communications is insidious: it reflects a well-informed approach to targeting the Syrian opposition with social engineering.
Attacks similar to this are complemented by others using intriguing political or religious content, and other forms of social engineering. Such attacks have been extensively analyzed by my Citizen Lab colleague Morgan Marquis-Boire and reported by Eva Galperin of the EFF, as well as many other researchers. The most recent joint Citizen Lab and EFF report (December 2013) can be found here.
Actions to Take
The developers of Psiphon were notified of the malware and suggest concerned users take the following steps (content adapted from their website).
- Check your copy of Psiphon for windows by following these simple steps outlined by Psiphon on their website:
- Right click on the Psiphon icon and select “Properties”
- You should see a “Digital Signatures” tab. Click it. If you do not see this tab, you may be looking at malware.
- Examine the Digital Signatures Tab. Does it look like the image below? (Click for larger image)
- Psiphon’s website states:”The SHA1 thumbprint for the Psiphon Inc. certificate public key is displayed in the Certificate dialog Details tab. For the certificate valid for the period June 16, 2011 to June 21, 2012 the SHA1 thumbprint is:
8f:b7:ef:bd:20:a9:20:3a:38:37:08:a2:1e:0a:1d:2e:ad:7b:ee:6dThe certificate valid for the for the period May 21, 2011 to July 30, 2014 the SHA1 thumbprint is:
84:c5:13:5b:13:d1:53:96:7e:88:c9:13:86:0e:83:ee:ef:48:8e:91Psiphon for Windows auto-updates itself, and this process automatically verifies that each update is authentic.”
- Note: while the malware does drop a working copy of Psiphon 3 (with a digital signature), it will be in a different directory than the one you executed Psiphon from (C:\Users\[USER]\AppData\Local\Temppsiphon3.exe)
- The developers of Psiphon encourage anyone interested in Psiphon 3 to take these steps to ensure their copy of Psiphon is genuine. If in doubt, send a blank email to firstname.lastname@example.org to receive a new copy. Any questions for Psiphon’s developer team can be sent to email@example.com.
In addition, while the malicious packaging results in a working copy of Psiphon and has a visually indistinguishable icon, the malware also leaves a number of files, any of which should be considered strong evidence of an infection. Here are several to watch out for:
If these files are found, Machines should be disconnected from the internet and reformatted. Additionally, users should take immediate steps to secure their accounts, as well as contacting others whose sensitive information may have been incidentally exposed.
In addition to these recommendations, we also suggest that, when possible, users make use of 2 factor authentication.
- To learn more about how to enable 2-Factor Authentication, see the links below for guides on how to do this on Facebook, Gmail and Twitter.
We note, however, that it is difficult for users in Syria to implement 2 factor authentication. The Google Play store is blocked for Syrian users by Google because of current Sanctions and Export Control regulations. This makes it difficult to obtain the 2-factor authentication app. Use of SMS messages as an alternative may present an unacceptable risk of exposure to surveillance. This remains an unresolved problem.
Psiphon Team and Karl Kathuria, Nart Villeneuve (FireEye) for first conclusively identifying this as njRAT, Morgan Marquis-Boire (Citizen Lab), Seth Hardy (Citizen Lab) and Irene Poetranto (Citizen Lab).