PGPCoder
Gpcode | |
---|---|
Technical name |
|
Classification | Trojan |
PGPCoder or GPCode is a trojan that encrypts files on the infected computer and then asks for a ransom in order to release these files, a type of behavior dubbed ransomware or cryptovirology.
Trojan
Once installed on a computer, the trojan creates two registry keys: one to ensure it is run on every system startup, and the second to monitor the progress of the trojan in the infected computer, counting the number of files that have been analyzed by the malicious code.
Once it has been run, the trojan embarks on its mission, which is to encrypt, using a digital encryption key, all the files it finds on computer drives with extensions corresponding to those listed in its code. These extensions include .doc, .html, .jpg, .xls, .zip, and .rar.
The blackmail is completed with the trojan dropping a text file in each directory, with instructions to the victim of what to do. An email address is supplied through which users are supposed to request for their files to be released after paying a ransom of $100–200 to an e-gold or Liberty Reserve account.[1]
Efforts to combat the trojan
While a few Gpcode variants have been successfully implemented,[2] many variants have flaws that allow users to recover data without paying the ransom fee. The first versions of Gpcode used a custom-written encryption routine that was easily broken.[3] Variant Gpcode.ak writes the encrypted file to a new location, and deletes the unencrypted file, and this allows an undeletion utility to recover some of the files. Once some encrypted+unencrypted pairs have been found, this sometimes gives enough information to decrypt other files.[4][5][6] Variant Gpcode.am uses symmetric encryption, which made key recovery very easy.[7] In late November 2010, a new version called Gpcode.ax[8] was reported. It uses stronger encryption (RSA-1024 and AES-256) and physically overwrites the encrypted file, making recovery nearly impossible.[9]
Kaspersky Lab has been able to make contact with the author of the program, and verify that the individual is the real author, but have so far been unable to determine his real world identity.[10]
References
- ^ Eran Tromer. "Cryptanalysis of the Gpcode.ak ransomware virus" (PDF). Retrieved 2008-09-30.
- ^ "Kaspersky Lab announces the launch of Stop Gpcode, an international initiative against the blackmailer virus". 2008-06-09.
- ^ "Blackmailer: the story of Gpcode". Kaspersky Labs. 2006-07-26.
- ^ "Utilities which fight Virus.Win32.Gpcode.ak". Kaspersky Lab. 2008-06-25.
- ^ "Restoring files attacked by Gpcode.ak". Kaspersky Labs. 2008-06-13. Archived from the original on 2009-07-13. Retrieved 2008-09-30.
- ^ "Another way of restoring files after a Gpcode attack". 2008-06-26. Archived from the original on 2013-02-09.
- ^ "New Gpcode - mostly hot air". Kaspersky Labs. 2008-08-14. Archived from the original on 2012-09-18.
- ^ "GpCode Ransomware 2010 Simple Analysis". Xylibox. 2011-01-30.
- ^ "GpCode-like Ransomware Is Back". Kaspersky Labs. 2010-11-29.
- ^ "Police 'find' author of notorious virus". TechWorld. 2008-09-30.
External links
- Kaspersky Lab
- Kaspersky Lab blog posts
- Kaspersky Lab forum dedicated to GPCode
- Kaspersky Lab virus descriptions
- StopGPCode trojan removal utilities
- Other virus description databases
- F-Secure
- Symantec
- McAfee: GPCoder GPCoder.e GPCoder.f GPCoder.g GPCoder.h GPCoder.i
- Trend Micro: TROJ_PGPCODER.A TROJ_PGPCODER.B TROJ_PGPCODER.C TROJ_PGPCODER.D TROJ_PGPCODER.E TROJ_PGPCODER.F TROJ_PGPCODER.G
- ThreatExpert
- v
- t
- e
← 1990s | Timeline | 2010s → |
2004 |
|
---|---|
2005 | |
2007 |
|
2008 |
|
2009 |
|
- Ac1db1tch3z
- Anonymous
- Avalanche
- GNAA
- 0x1fe
- GhostNet
- Level Seven
- PLA Unit 61398
- RBN
- ShadowCrew
- World of Hell
- Sandworm
- AKill
- Jeanson James Ancheta
- SilenZ
- Dshocker
- Digerati
- str0ke (milw0rm)
- Lil Hacker
- BadB
- camZero
- Coolio
- Cyxymu
- diabl0
- Albert Gonzalez
- Sven Jaschan
- Dan Kaminsky
- Samy Kamkar
- Dmitry Sklyarov
- Stakkato
- Bluehell IRC
- ryan1918
- unkn0wn.eu
- darksun.ws
discovered
- Shatter attack (2002)
- Kaminsky DNS cache poisoning (2008)
- sslstrip (2009)
2000 | |
---|---|
2001 | |
2002 |
|
2003 |
|
2004 |
|
2005 |
|
2006 | |
2007 |
|
2008 | |
2009 |