Hi friends,
I hope you're all doing great. I have a few days off myself, I'm due to start at a new job next week so it's good to have a bit of space in between. I'm very excited to start though, and I'll tell you more about it once I get going there :-)
In the mean time I hope you get value out of this week's issue, and see you all next week! Have a good one!
Nice writeup of statistics and trends that we're seeing in ransomware payments and groups. There's good news, for example that a smaller share of victims are paying ransom. But overall revenue for ransomware operators is up, unfortunately, because they're attacking more targets.
If you like statistics, the following article has some more. This time from Mandiant on how they've seen median dwell time drop, which is good progress: link.
This definitely raised my eyebrows. There's a mechanism in Github that is ripe for abuse, and in fact is being abused as we speak.
You can go to a public repo of a well known company, like Microsoft, write a comment on an issue somewhere, and upload an attachment to that comment. That attachment will then look like github.com/microsoft/repo/files/legitlooking.zip.
If you give that file the same name as, for example, a driver, even I would believe at a glance that it's a legit link to a release artifact. But unfortunately anyone can generate them. In fact, you don't even have to post the comment for it to work. Once you upload the file it remains in existence, even if you cancel the comment. So far, Github hasn't tackled this issue yet, although I assume/hope that they soon will.
Since this article it's become known that Gitlab has the same issue: link.