Bitcrypt broken
Jump to navigation
Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
(Publication) Google search: [1]
| Bitcrypt broken | |
|---|---|
| Botnet | Bitcrypt |
| Malware | |
| Botnet/malware group | |
| Exploit kits | |
| Services | |
| Feature | |
| Distribution vector | |
| Target | |
| Origin | |
| Campaign | |
| Operation/Working group | |
| Vulnerability | |
| CCProtocol | |
| Date | 2014 / 2014-02-20 |
| Editor/Conference | Cassidian Cybersecurity |
| Link | http://blog.cassidiancybersecurity.com/post/2014/02/Bitcrypt-broken (Archive copy) |
| Author | Cédric Pernet, Fabien Perigaud |
| Type | Blogpost |
Abstract
“ Now this is all theoric. Everything changes when someone you know is hit by this kind of malware. This is what happened to one of us. One very close friend just got infected with a brand new piece of ransomware called BitCrypt and you know what? That nasty piece of malware encrypted all pictures of his lovely children from their birth to now. No backup, except for some pictures on Facebook. Now we feel very concerned, because one of us is the godfather of one of those adorable kids, a rock'n'roll boy called Keziah.
Bibtex
@misc{Lua error: Cannot create process: proc_open(/dev/null): failed to open stream: Operation not permitted2014BFR1378,
editor = {Cassidian Cybersecurity},
author = {Cédric Pernet, Fabien Perigaud},
title = {Bitcrypt broken},
date = {20},
month = Feb,
year = {2014},
howpublished = {\url{http://blog.cassidiancybersecurity.com/post/2014/02/Bitcrypt-broken}},
}