News for hackers. Stuff that matters.
Re:New ransomware written in JavaScript discovered by toyg on Monday June 20, 2016 @05:19AM (#11936966)
Not "completely", there are ways to disable this sort of thing with AD policies. This corner of Windows has been de-emphasized ever since the "security push" of XPsp2, and it's all but been replaced by Powershell. Microsoft being Microsoft, they have not completely removed cscript.exe for compatibility reasons but they'll likely do it at some point.

In fact, I bet this "exploit" doesn't work on a properly-secured box with UAC on where a user is not running as a local admin, at least not for the part about Volume Shadow Copy.

It's a shame because I personally like CScript/WScript, it's the little scripting engine that could. Unfortunately, the Windows security model is too haphazard to let something like this free to run.

Re:New ransomware written in JavaScript discovered by emodendroket on Monday June 20, 2016 @08:52AM (#11937621)
In Korea banks, by law, have to secure their Web sites with ActiveX plugins, which probably means this stuff is going to be around way longer than it should be.
Re:New ransomware written in JavaScript discovered by nubianwarrior on Monday June 20, 2016 @11:23AM (#11938589)
This. South Korea's insistence on using 2001 technologies today has made Windows almost unmanageable in a highly secure environment.
Re:New ransomware written in JavaScript discovered by emodendroket on Monday June 20, 2016 @11:30AM (#11938637)
Can't you block ActiveX altogether through GP? I mean... doesn't help if you're in Korea, but for the rest of us.
Re:New ransomware written in JavaScript discovered by excalibur on Monday June 20, 2016 @11:50AM (#11938795)
Thanks for the reminder. I disabled scripting via GPO for this reason months ago, but I forgot to actually remove the logon scripts from all of the AD accounts. This mechanism has become largely redundant anyway, tasks like drive and printer mapping are better done in other ways.