Open Source 2016-08-28 · 2 days ·Data Exfiltration

Transmission installer delivered Keydnap

Months after the KeRanger incident, Transmission's website was compromised again. This time, the legitimate macOS installer for version 2.92 was replaced with a malicious version containing the OSX/Keydnap backdoor.

Story

The August 2016 Transmission compromise repeated the same distribution pattern with a different payload. A recompiled Transmission 2.92 application was served from the official site and carried OSX/Keydnap instead of ransomware.

The malicious disk image was named Transmission2.92.dmg, while the legitimate package used Transmission-2.92.dmg. Inside the app bundle, the added License.rtf file acted as the dropper. ESET reported that the bundle was signed on August 28 with an Apple-issued certificate that was not the normal Transmission developer certificate.

Keydnap installed persistence under com.apple.iCloud.sync.daemon, used a local Tor client to reach an onion command server, and targeted the macOS keychain. Its purpose was quiet control and credential theft, not visible encryption.

ESET notified the Transmission team, which removed the file within minutes and moved users toward clean downloads. The second incident showed that the March response fixed the immediate artifact, not necessarily the release channel risk.

Affected Artifacts

transmission

· transmissionbt.com · repository · Binary Archive
Observed
2016-08-28 to 2016-08-30
Compromised Versions
Fixed
Not listed
Hashes
  • sha256:f06ac9609c3a8b00a7586840e990153460f8de9526e91a1a6ab733c850d5c83f
  • sha256:c5e5ec89c5517b50d848b6a6d4f86ed74715a715a015c6d38d789addcffea6b3
  • sha1:1ce125d76f77485636ecea330acb038701ccc4ce
  • +2 more

Incident Context

Motive
Credential Theft
Attribution
Group
Cause
Compromised Infrastructure
Transitive
No
Actor
Cybercriminal Gang

External References

Source record: oss/attacks/transmission/2016-08/meta.yaml