Erebus is a ransomware family with Windows and Linux builds. The first version, seen in September 2016, was pushed through malicious ads leading to the RIG exploit kit; it adds the .ecrypt extension and renames files to a hash. A February 2017 Windows build skips a fixed extension and instead scrambles the original extension with ROT-23, so .pdf becomes .msj. It leaves README.html on the desktop and in Documents, asks 0.085 bitcoin within 96 hours through a Tor site, slips past User Account Control and deletes shadow copies. In June 2017 a Linux build appeared that renames files to random names ending in .ecrypt and starts itself through a fake bluetooth service and an hourly cron job. The Linux build hit 153 servers belonging to a hosting provider in South Korea, affecting websites, databases and media for about 3,400 business customers, and the company agreed to pay. That build targets more than 430 file types, including Office files, databases, archives, mail and web project files. No theft of victim files is documented and there is no leak site. The two Windows builds differ a great deal and may not share code.
Sources: In-house research
File extensions: .ecrypt
Ransom note filenames: README.html
Decryptor: No public decryptor was found.
Data exfiltration risk: Undocumented — The Linux build sends system details and its key material to the operators, but no theft of victim files is documented for any Erebus version, and there is no leak site.
Systems typically targeted: Windows PCs in 2016 and early 2017, then Linux web servers from June 2017, where it went after site files, databases including MySQL InnoDB data files, and media.
Do this first: The Linux build restarts itself through a fake bluetooth init script and an hourly cron entry, so clean both or restored data will be encrypted again. Keep the ransom note files and a few encrypted samples, and check database files such as ibdata and ib_logfile first. On Windows, the 2017 build deletes shadow copies, so restore from separate backups.
Dealing with an active incident? Our incident response team is available 24/7.
Emergency response: +1 (877) 364-5161