Difference between revisions of "ZeroLocker won't come to your rescue"

From Botnets.fr
Jump to navigation Jump to search
m (Remplacement de texte — « Kaspersky lab lab » par « Kaspersky lab »)
 
m (Text replacement - " securelist.com" to "")
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Publication
{{Publication
|Link=http://securelist.com/blog/incidents/66135/zerolocker-wont-come-to-your-rescue/ securelist.com
|Link=http://securelist.com/blog/incidents/66135/zerolocker-wont-come-to-your-rescue/
|Author=Roel Schouwenberg
|Author=Roel Schouwenberg
|NomRevue=Securelist
|NomRevue=Securelist

Latest revision as of 18:47, 8 February 2015

(Publication) Google search: [1]

ZeroLocker won't come to your rescue
Botnet ZeroLocker
Malware
Botnet/malware group
Exploit kits
Services
Feature
Distribution vector
Target
Origin
Campaign
Operation/Working group
Vulnerability
CCProtocol
Date 2014 / 2014-08-18
Editor/Conference Kaspersky lab
Link http://securelist.com/blog/incidents/66135/zerolocker-wont-come-to-your-rescue/ (Archive copy)
Author Roel Schouwenberg
Type

Abstract

One of the new ones we've seen pop up in the last couple weeks is called ZeroLocker. There's indication the C&C configuration contains some errors which would prevent successful decryption. This is why we urge people not to pay up even more so than normal.

So far we've observed a limited amount of detections through our Kaspersky Security Network. The actors behind ZeroLocker are initially asking $300 worth of BTC for decrypting the files. This goes up to $500 and $1000 as time passes:

Bibtex

 @misc{Lua error: Cannot create process: proc_open(/dev/null): failed to open stream: Operation not permitted2014BFR1398,
   editor = {Kaspersky lab},
   author = {Roel Schouwenberg},
   title = {ZeroLocker won't come to your rescue},
   date = {18},
   month = Aug,
   year = {2014},
   howpublished = {\url{http://securelist.com/blog/incidents/66135/zerolocker-wont-come-to-your-rescue/}},
 }