vendor binary

The Transmission 2.90 KeRanger Ransomware Attack

Updated 5 Oct 2026 · Incident date 4 Mar 2016

Transmission-2.90.dmg from the official site carried KeRanger, the first fully working ransomware seen on OS X, on 4 and 5 March 2016.

Palo Alto Networks found it on 4 March 2016. The ransomware waits three days before it contacts its servers and encrypts files.

What happened

The official Transmission 2.90 download contained a program disguised as a document.

  • The file General.rtf in Transmission.app/Contents/Resources/ was a Mach-O executable, not a document.
  • A valid Apple developer certificate signed the installer, so Gatekeeper did not block it. Apple revoked the certificate later.
  • When the app ran, it copied the executable to ~/Library/kernel_service and started it.
  • After three days it contacted command servers on Tor and encrypted files with RSA and AES.
  • It asked for one bitcoin, about 400 US dollars, and left README_FOR_DECRYPT.txt in each folder.

The infection window ran from 11:00 AM PST on 4 March to 7:00 PM PST on 5 March 2016.

Affected versions

  • Transmission for Mac 2.90, as Transmission-2.90.dmg.
  • Downloaded from the official site from 11:00 AM PST on 4 March to 7:00 PM PST on 5 March 2016.
  • Version 2.89 was clean. The sources do not name the fixed release number.

Indicators of compromise

  • File /Applications/Transmission.app/Contents/Resources/General.rtf.
  • Process kernel_service and file ~/Library/kernel_service.
  • Files ~/Library/.kernel_pid, ~/Library/.kernel_time and ~/Library/.kernel_complete.
  • Ransom note README_FOR_DECRYPT.txt and the .encrypted file extension.
  • Tor addresses: lclebb6kvohlkcml.onion[.]link, bmacyzmea723xyaz.onion[.]link and nejdtkok7oz5kjoc.onion[.]link.
  • SHA-256 values listed by Unit 42: d1ac55a4e610380f0ab239fcc1c5f5a42722e8ee1554cba8074bbae4a5f6dbe1, e3ad733cea9eba29e86610050c1a15592e6c77820927b9edeb77310975393574, 31b6adb633cff2a0f34cefd2a218097f3a9a8176c9363cc70fe41fe02af810b9, d7d765b1ddd235a57a2d13bd065f293a7469594c7e13ea7700e55501206a09b5, ddc3dbee2a8ea9d8ed93f0843400653a89350612f2914868485476a847c6484a and 6061a554f5997a43c91f49f8aaf40c80a3f547fc6187bee57cd5573641fcf153.

How to check

Look for the fake document and the dropped files. If General.rtf is present, run file on it. A real document is not a Mach-O executable.

ls -la /Applications/Transmission.app/Contents/Resources/General.rtf ~/Library/kernel_service ~/Library/.kernel_*

Look for the running process. A match means the Mac ran KeRanger.

pgrep -l kernel_service

What to do now

  1. Quit Transmission and delete Transmission.app if it is version 2.90.
  2. Delete ~/Library/kernel_service and the .kernel_pid, .kernel_time and .kernel_complete files.
  3. If files are encrypted, restore them from a backup. The sources report no free decryption at that time.
  4. Install a current release from the official site. Compare its hash with the one the project publishes.

Frequently asked questions

What files did KeRanger target?

Unit 42 says it targeted more than 300 file extensions. BleepingComputer reports that it scanned /Users and /Volumes, including external drives.

How many victims did KeRanger have?

Wikipedia reports more than 7,000 victims.

Sources

  1. unit42.paloaltonetworks.com/new-os-x-ransomware-keranger-infected-transmission-bittorrent-client-installer/
  2. bleepingcomputer.com/news/security/information-about-the-keranger-os-x-ransomware-and-how-to-remove-it/
  3. en.wikipedia.org/wiki/KeRanger

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library