Found via a link on Spiceworks forums....
https://docs.google.com/spreadsheets/u/1/d/1TWS238xacAto-fLKh1n5uTsdijWdCEsGIM0Y0Hvmc5g/htmlview?sle...
A nice list of all the ransomwares and even decryption solutions for some of them!
Found via a link on Spiceworks forums....
https://docs.google.com/spreadsheets/u/1/d/1TWS238xacAto-fLKh1n5uTsdijWdCEsGIM0Y0Hvmc5g/htmlview?sle...
A nice list of all the ransomwares and even decryption solutions for some of them!
Gavin / xpd / FastRaccoon / Geek of Coastguard New Zealand
![]() ![]() ![]() |
|
I would give a significant amount to have these 'people' shut down for good.
“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams
Referral links to services I use, really like, and may be rewarded if you sign up:
PocketSmith for budgeting and personal finance management. A great Kiwi company.
Dynamic:
I would give a significant amount to have these 'people' shut down for good.
Then more 'people' would just take their place. Its just crime, the chances of shutting down crime = zero.
Its what happens when you have very highly educated people earning extremely low wages .
Its also what happens when you have stupid or careless people using PC's and companies with no real training .
The best way to shut them down is to stop it from being run on PC's , and stop people from paying.
with no reward they will be less likely to keep writing so much new ransomware.
“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams
Referral links to services I use, really like, and may be rewarded if you sign up:
PocketSmith for budgeting and personal finance management. A great Kiwi company.
Dynamic: This approach of course only works after the servers have been discovered so it is always on the trailing edge. Consider googling cryptoprevent.
Works if it's the old style that tries to write .exe files and execute them from temp paths, but the new style are much smarter and write into folders off the root.
Dynamic: This approach of course only works after the servers have been discovered so it is always on the trailing edge. Consider googling cryptoprevent.
Not necessarily - a lot of them use an algorithm to generate the c & c domains, OpenDNS and others reverse engineer these.
Best defense as always - keep everything up to date and have good backups.
wasabi2k:
Dynamic: This approach of course only works after the servers have been discovered so it is always on the trailing edge. Consider googling cryptoprevent.
Not necessarily - a lot of them use an algorithm to generate the c & c domains, OpenDNS and others reverse engineer these.
Best defense as always - keep everything up to date and have good backups.
Up to date does provide little defense these days, we have seen completely up to the minute systems compromised many times this year.
The problem is there are now online kits for making your own "cryptolocker" with nice gui's etc to guide you through, and the AV and Malware vendors aren't even close to keeping up sadly.
networkn:
wasabi2k:
Dynamic: This approach of course only works after the servers have been discovered so it is always on the trailing edge. Consider googling cryptoprevent.
Not necessarily - a lot of them use an algorithm to generate the c & c domains, OpenDNS and others reverse engineer these.
Best defense as always - keep everything up to date and have good backups.
Up to date does provide little defense these days, we have seen completely up to the minute systems compromised many times this year.
The problem is there are now online kits for making your own "cryptolocker" with nice gui's etc to guide you through, and the AV and Malware vendors aren't even close to keeping up sadly.
Its just the whole RAT issue all over again really. Give it a few years, and there will be the new fab on the block...
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
networkn:wasabi2k:Dynamic: This approach of course only works after the servers have been discovered so it is always on the trailing edge. Consider googling cryptoprevent.Not necessarily - a lot of them use an algorithm to generate the c & c domains, OpenDNS and others reverse engineer these.
Best defense as always - keep everything up to date and have good backups.
Up to date does provide little defense these days, we have seen completely up to the minute systems compromised many times this year.
The problem is there are now online kits for making your own "cryptolocker" with nice gui's etc to guide you through, and the AV and Malware vendors aren't even close to keeping up sadly.
Kiwifruta:
DIY cryptolocker, flippin' heck, horrific. Imagine what little Johnny at school could do with that.
I could tell far too many stores on this that landed in big trouble...
not sure i particularly wanna detail and have a younger reader catch on and try anything themselves though!
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77:Kiwifruta:
DIY cryptolocker, flippin' heck, horrific. Imagine what little Johnny at school could do with that.I could tell far too many stores on this that landed in big trouble...
not sure i particularly wanna detail and have a younger reader catch on and try anything themselves though!
Kiwifruta:hio77:
Kiwifruta:
DIY cryptolocker, flippin' heck, horrific. Imagine what little Johnny at school could do with that.
I could tell far too many stores on this that landed in big trouble...
not sure i particularly wanna detail and have a younger reader catch on and try anything themselves though!
Definitely needs to be blocked from a google search.
Sadly, once you start down the road of "blocking searches" it's a slippery slope.
networkn:
Sadly, once you start down the road of "blocking searches" it's a slippery slope.
same goes for "blocking proxies" bye bye google translate..
or how about "blocking porn" bye bye google images...
funny how the hammer approach hits so often...
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
|
![]() ![]() ![]() |