4 ms·

Site is currently down; https://web.archive.org/web/20200122181519/https://blogs.quickheal.com/first-node-js-based-ransomware-nodera/ https://web.archive.org/we

Site is currently down; https://web.archive.org/web/20200122181519/https://blogs.quickheal.com/first-node-js-based-ransomware-nodera/ https://web.archive.org/web/20200122181519/https://blogs.qui... The article mentions the ransom message with the date March 1 2018. This probably means this malware is two years old?

ecmascript 7y ago
Ironically, the archive link you provided also doesn't load for me.
- deleted 7y ago
  [deleted]
- msla 7y ago
  If it's just a blank screen, it's a longstanding issue nobody seems to acknowledge: https://news.ycombinator.com/item?id=21765389 https://news.ycombinator.com/item?id=21765389 > There's a problem with the Wayback Machine in specific which can kill your ability to access it quite silently, unless you know how to use the browser's development tools and interpret headers. > It has to do with cookies: Somehow, the Wayback Machine sets cookies... and sets cookies... and keeps setting cookies, until it overflows its own ability to accept cookies. At that point, your browser tries to access a Wayback Machine page, handing the server all of the cookies it currently has, and the server refuses to deal. It absolutely denies everything, sending an error header and a blank page. You have to clear all web.archive.org cookies to get anything at all, at which point it works perfectly. > I've completely solved this problem by blacklisting web.archive.org in browser cookie blacklists. I haven't had it happen since then. As far as I'm concerned, the problem is diagnosed and just needs to be solved. At their end.
grammarxcore 7y ago
> This ransomware seems to be in development phase and has some flaws as mentioned below: > ... > Hard code destruction time of Private Key “March 1 2018”. Quite possibly. I'm not sure what that language means and they don't provide more analysis of the HTML page that comes from. If it's in development maybe some dude has been sitting on this idea for a few years and their virus scanner just picked it up recently.

ecmascript 7y ago

Ironically, the archive link you provided also doesn't load for me.

deleted 7y ago
[deleted]
msla 7y ago
If it's just a blank screen, it's a longstanding issue nobody seems to acknowledge: https://news.ycombinator.com/item?id=21765389 https://news.ycombinator.com/item?id=21765389 > There's a problem with the Wayback Machine in specific which can kill your ability to access it quite silently, unless you know how to use the browser's development tools and interpret headers. > It has to do with cookies: Somehow, the Wayback Machine sets cookies... and sets cookies... and keeps setting cookies, until it overflows its own ability to accept cookies. At that point, your browser tries to access a Wayback Machine page, handing the server all of the cookies it currently has, and the server refuses to deal. It absolutely denies everything, sending an error header and a blank page. You have to clear all web.archive.org cookies to get anything at all, at which point it works perfectly. > I've completely solved this problem by blacklisting web.archive.org in browser cookie blacklists. I haven't had it happen since then. As far as I'm concerned, the problem is diagnosed and just needs to be solved. At their end.

grammarxcore 7y ago

> This ransomware seems to be in development phase and has some flaws as mentioned below: > ... > Hard code destruction time of Private Key “March 1 2018”. Quite possibly. I'm not sure what that language means and they don't provide more analysis of the HTML page that comes from. If it's in development maybe some dude has been sitting on this idea for a few years and their virus scanner just picked it up recently.