It's sorta strange seeing this here today, since I'm not aware of anything happening with Salsa20 lately. But for people that are interested, the Petya ransomwa

It's sorta strange seeing this here today, since I'm not aware of anything happening with Salsa20 lately. But for people that are interested, the Petya ransomware that was running around a couple months ago used a borked version of Salsa20[1], returning 16-bit values instead of 32 bit values, which lead people to break it [2][3]. Moral of the story: don't roll your own crypto, even when you're a malware author. [1]: http://blog.checkpoint.com/2016/04/11/decrypting-the-petya-ransomware/ http://blog.checkpoint.com/2016/04/11/decrypting-the-petya-r... [2]: https://github.com/leo-stone/hack-petya https://github.com/leo-stone/hack-petya [3]: https://0xec.blogspot.com/2016/04/reversing-petya-ransomware-with.html https://0xec.blogspot.com/2016/04/reversing-petya-ransomware...