Live data from Hacker News

Apple has shut down the first fully-functional Mac OS X ransomware

techcrunch.com

11–20 of 30 posts

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#11

> The fact that OS X has now been targeted speaks to the popularity of Apple’s operating system It's not a security breach it's a problem of rising popularity. That's one way to spin it.

It is a security breach but in the past most malware has been targeting windows because of the larger financial upside due to popularity. As OS X gets more popular expect more attempts like this.

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#12
post #10
post #5

Earlier quoted context omitted.

Do you have a citation for this? The extent of what was illicitly accessed remains unclear. Without knowing how their infrastructure is set up, it's not possible to say that the intrusion was limited to just the web server.

Here's the Reuters article where they state that: http://www.reuters.com/article/apple-ransomware-idINL1N16F17...

Thanks for that, at least it's something. John Clay is listed here[1] as a contributor to "Website maintenance and troubleshooting, Mac OS X help documentation". I wish they would post a similar update on their website and explicitly confirm that the current source and binaries have been audited and are safe.

[1] https://github.com/jparyani/Transmission/blob/master/AUTHORS

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#13

> The fact that OS X has now been targeted speaks to the popularity of Apple’s operating system It's not a security breach it's a problem of rising popularity. That's one way to spin it.

It is a security breach but in the past most malware has been targeting windows because of the larger financial upside due to popularity. As OS X gets more popular expect more attempts like this.

You don't think it has anything to do with the fact that OSX is more secure than Windows due to the underlying OS being based on FreeBSD? The economics have been in favor of attacking OSX for along time now. Especially when you consider that OSX users likely have more money on average since OSX adoption has been much higher among the affluent.

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#14

> The fact that OS X has now been targeted speaks to the popularity of Apple’s operating system It's not a security breach it's a problem of rising popularity. That's one way to spin it.

It is a security breach but in the past most malware has been targeting windows because of the larger financial upside due to popularity. As OS X gets more popular expect more attempts like this.

[deleted]

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#15
post #8

So this confirms that Apple revoking the app-signing certificate that pissed off a bunch of people was related to KeRanger?

No. They revoked that single developer's certificate. I think you're referring to an Apple certificate that simply expired and invalidated many App Store signatures.

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#16
post #5

Earlier quoted context omitted.

Someone compromised their main web server where the binaries are hosted and put up a malicious binary.

Do you have a citation for this? The extent of what was illicitly accessed remains unclear. Without knowing how their infrastructure is set up, it's not possible to say that the intrusion was limited to just the web server.

They've probably addressed it officially by now, but the malware was only included in v2.9.0 downloaded from the web page directly. It wasn't included if the update was performed through the Transmission client. That would seem to suggest it was the web server that was compromised.

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#17

"...has shut down the first fully-functional Mac OS X ransomeware" Here I was hoping it was the second malware coded with functional programming. Scheme last time [1]. I was hoping to see some systems Haskell or ATS in there. Oh well. Always another opportunity when it comes to malware. [1] http://philosecurity.org/2009/01/12/interview-with-an-adware...

>Windows has this thing called Create Remote Thread. Basically, the semantics of Create Remote Thread are: You’re a process, I’m a different process. I call you and say “Hey! I have this bit of code. I’d really like it if you’d run this.” You’d say, “Sure,” because you’re a Windows process– you’re all hippie-like and free love. Windows processes, by the way, are insanely promiscuous. So! We would call a bunch of processes, hand them all a gob of code, and they would all run it.

I...wait, what? Did Windows actually used to be that bad?

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#18

"...has shut down the first fully-functional Mac OS X ransomeware" Here I was hoping it was the second malware coded with functional programming. Scheme last time [1]. I was hoping to see some systems Haskell or ATS in there. Oh well. Always another opportunity when it comes to malware. [1] http://philosecurity.org/2009/01/12/interview-with-an-adware...

>Windows has this thing called Create Remote Thread. Basically, the semantics of Create Remote Thread are: You’re a process, I’m a different process. I call you and say “Hey! I have this bit of code. I’d really like it if you’d run this.” You’d say, “Sure,” because you’re a Windows process– you’re all hippie-like and free love. Windows processes, by the way, are insanely promiscuous. So! We would call a bunch of proc…

This still exists, and it's used by lots of extensions.

But you can only inject DLLs (this is how it's called) if your process already has some admin rights and if the other process is not of a higher integrity.

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#19

"...has shut down the first fully-functional Mac OS X ransomeware" Here I was hoping it was the second malware coded with functional programming. Scheme last time [1]. I was hoping to see some systems Haskell or ATS in there. Oh well. Always another opportunity when it comes to malware. [1] http://philosecurity.org/2009/01/12/interview-with-an-adware...

>Windows has this thing called Create Remote Thread. Basically, the semantics of Create Remote Thread are: You’re a process, I’m a different process. I call you and say “Hey! I have this bit of code. I’d really like it if you’d run this.” You’d say, “Sure,” because you’re a Windows process– you’re all hippie-like and free love. Windows processes, by the way, are insanely promiscuous. So! We would call a bunch of proc…

Well, the remote process has to have been launched with the appropriate permissions to allow remote threads. Also the remote thread can only run code which already exists in the remote process, though one common trick is to call LoadLibrary to inject a custom DLL.

Re: Apple has shut down the first fully-functional Mac OS X ransomware

#20
post #15
post #8

So this confirms that Apple revoking the app-signing certificate that pissed off a bunch of people was related to KeRanger?

No. They revoked that single developer's certificate. I think you're referring to an Apple certificate that simply expired and invalidated many App Store signatures.

They revoked the developer's certificate, or they blocked opening up of an image with a given checksum?
Post reply on HN