Live data from Hacker News

University pays $20,000 to ransomware hackers

bbc.co.uk

41–50 of 80 posts

Re: University pays $20,000 to ransomware hackers

#41

Easy solution - the government writes into law it's illegal to pay ransomware hackers. Sure hackers might get the occasional payee after this but the likelihood goes down dramatically removing much incentive, especially for larger organisations to be targeted.

Or let nature take its course and let this lead to improved data and security practices.

Re: University pays $20,000 to ransomware hackers

#42

Microsoft really needs to build ransomware behavior detection directly into Windows. The behavior of these programs is quite distinctive. The advent of cryptocurrency was the missing link to enable all manner of anonymous extortion schemes, and this one in particular seems to now be a mainstream threat. Microsoft should be all over this.

Exactly what I was thinking too.

Re: University pays $20,000 to ransomware hackers

#43

If you're a Windows programmer, might be a good idea to write a Windows Service that watches for drive encryption. Then you could stop it before it does anything. For now, I think most of the methods are known, so they are easy to watch for.

IMO, Micro$oft can gain a huge amount of positive press/PR as well as user-love by integrating a defense/protection mechanism right into the OS.

Re: University pays $20,000 to ransomware hackers

#44

Earlier quoted context omitted.

Ransomware detection is just a (perhaps necessary) band-aid. By default all applications should be sandboxed. Why should a random application be able to read/write to every user directory? We enforce process separation in memory, we should do the same on disk.

> all applications should be sandboxed. not a bad plan, but also, all data should be backed up . In this 'cloud age' of computing, there's no reason, and no excuse. I certainly don't want to blame the victims of ransomware, but if that data was so important that they paid ransom to get it back, why didn't they back it up ?

Except the way most people do backups, by the time they are made aware of the ransom, their backup files are already overwritten with the encrypted ones.

Re: University pays $20,000 to ransomware hackers

#45

Earlier quoted context omitted.

Ransomware detection is just a (perhaps necessary) band-aid. By default all applications should be sandboxed. Why should a random application be able to read/write to every user directory? We enforce process separation in memory, we should do the same on disk.

That's exactly what UWP(universal windows platform) is - it sandboxes every app. But I am sure you will agree that having this as default behavior on windows would be disastrous, breaking compatibility with every app written before Windows 10, not to mention that the reason why we use PCs is to have low-level access to hardware, many applications require it and sandboxing isn't going to be a good option here. I guess…

If you search online Mac forums many people ask how to disable such features.

For average joe and jane security is a nuisance.

Re: University pays $20,000 to ransomware hackers

#48
Since this exploits user level privileges, perhaps a good idea would be to have a privileged version control system for user data. In that, you need admin/root access to actually DELETE anything, and any file system changes by users are simply versioned away. This means if you had ransomware that fucked up your files (since this software typically runs at user level), you could just instruct said versioning system to roll everything back as an admin?

Re: University pays $20,000 to ransomware hackers

#49

If you're a Windows programmer, might be a good idea to write a Windows Service that watches for drive encryption. Then you could stop it before it does anything. For now, I think most of the methods are known, so they are easy to watch for.

IMO, Micro$oft can gain a huge amount of positive press/PR as well as user-love by integrating a defense/protection mechanism right into the OS.

The moment Microsoft try to be proactive and integrate a defence mechanism I would suspect people would then try to hold them liable if another ransomware attack succeeded.

Microsoft could do without the overhead, or the headache, and so despite the PR upside it's probably not worth their effort.

Might be an opportunity for an ISV to make a utility though?

Re: University pays $20,000 to ransomware hackers

#50
post #2

Why openly announce that you're paying the ransom? Here's some major disadvantages that I can think of: 1. Announces to world that you have poor security/backup practices which encourages more attacks against you 2. Announces to world that making and distributing ransomware is good business which encourages more attacks against everyone I understand that public institutions needs financial transparency in order to be…

I'm not really sure these threat scenarios apply when it comes to ransomware. Often ransomware attacks are not targeted but instead just the result of your standard drive-by attack or the classic shotgun e-mail approach, since usually university email listings are pretty easily scrape-able, especially if they're a Google Apps for Education (GAFE) university, as GAFE has pretty generous in-domain sending policies on email and there's an implicit trust in most people when they get something from an in-domain email.

So the initial point, while it may be true to some extent, is not really the common method of attack; the truth is that for the most part there is no need to really "craft" an attack against most users within a large enough organization. Just compromising one or two accounts or using one of many means to impersonate an official sounding account is often enough to get access to a few in-domain accounts. Once you have that, you can easily get past the majority of people's mistrust and get them to run just about anything you send them. When I did support for a small private university in the US, our GAFE accounts were constantly plagued by phishing and spam emails, and despite our best efforts to educate our user base, people just kept on clicking and giving out information. The entire process was basically automated from the attacker's side, as when we compared notes with other universities suffering the same issue, the emails sent out were verbatim copies, save that the university names were swapped out and a different logo.jpg was added to the emails for authenticity. Attacking a major organization really doesn't require a careful eye and dedication, just changing a few entries in some program and starting the process.

As for why to disclose? There's probably some degree of a necessary public accountability - I actually doubt that the university itself called up a paper and said "man have we got a story for you" so much as someone at the publication got wind of the information and plugged the university for a brief interview. Honestly, reading through the article, it's incredibly terse as far as actual details from the University as to what happened. Since it's a Canadian University, I'm not sure on their responsible disclosure requirements, but if it was in the US, I believe they have a timeframe in which they have to admit that student data has potentially been leaked.

Really, these sorts of impersonal attacks do need a lot more attention, since as recently as just a year ago, I found myself talking with somewhat major institutions around the US who had no real good idea how to deal with ransomware, (spear) phishing emails, and so on within their organization. Creating effective user awareness is really tough, since rather frustratingly, getting "phished" seems to be one of those lessons everyone wants to learn the hard way, or arrogantly thinks will never happen to them. We used a Twitter account in combination with a threat blog to try to notify our users, as well as warnings on our log-in page, but even after doing that for 4ish years we still had people giving out their information, and we had an okay-ish following on both.

I'm not saying that it was "good" of them to release that they decided to pay, but I also do question, given how easy ransomware is to deploy, whether or not more discretion would actually have a larger impact. Schools in particular are kind of over a barrel if/when they get hit by ransomware, and a lot of it has to do with poor data retention practices by both the University IT and by offices across the organization. Often times it's not just a mild inconvenience if someone's computer gets locked up by ransomware, you can potentially be irreparably damaging hundreds or more students' academic careers. Should this data be in a position that it can happen like this? Absolutely not, but that doesn't change the fact that it often is.

Post reply on HN