- Sep 17, 2013
- 1,492
i know that ransomware's encrypts file in the hard disk.
Is the ransomware capable of encrypting whole hard disk?
Is the ransomware capable of encrypting whole hard disk?
It can be done but it is not the most easiest thing for someone to do if they are not very XP.Besides, System Space = c:\program files, c:\program files (x86), c:\windows, etc, are protected resources by default in Windows and there is no way it should happen. If anyone finds a way to do it, then they're gonna make a lot money off of it -- either by reporting it to Microsoft and collecting a bug bounty or selling the vulnerability to enterprising criminals...
It's possible.. So you could edit things like boot sector and make the target provide the right decryption key at boot and pay the ransom to get the key from another system. So it encrypts the entire drive but leaving that boot sector so it can load itself to get the decryption key but you must pay ransom for the key from another system as the current one cant be booted in as the OS itself is encrypted.. maybe you will see what I mean
It can be done but it is not the most easiest thing for someone to do if they are not very XP.
Petya ransomware did things like edit the MBR and on boot made a fake checkup appear and encrypted files.. Something like that really![]()
I agree with you!I get that, but the way I interpreted the way the OP phrased the question was "Could ransomware encrypt the entire drive in-place -- without the whole MBR rigmarole." On the face of it, I think not -- at least not to keep a functional system - so as to pay the ransom.
Besides, Windows protects System Space from modification, but of course, I'm sure there are ways around that.
I searched, but could find no reported ransomware that encrypts the entire drive (complete file system - including all Windows "protected" resources).
What sense does it make to encrypt all *.exes and *.dlls on the system ? - that will remove any user access to browsers which = primary means to pay ransom.
It just makes no sense to keep boot load ability, but create an encrypted system with no ability to log-on, no networking and no functional browser.
It's possible, but not practical. It would be an act of sheer meanness - just for the sake of being mean and smashing a system completely.
I agree with you!
But if it was perfectly targeted to a noob audience they won't even know the system can't just be fixed after the key being entered then they'd probably still make money. But still I agree with you. I have just been thinking of random possibilities..![]()
Yes that should work well.. Against at least most ransomware. Another idea to strengthen your idea is to change the extensions of the really important documents to something random like *.viktik and remember the original extension to revert back when you need iti have few documents that very very important.
i was thinking to keep those documents in a separate partition. Then I will hide that partition using partition manager. Whenever i will need it, I will unhide the partition.
Malwares will not be able to see it. so they won't be able to steal or modify it.
i think this will greatly reduce the risk of losing my important files.
That wiped hard drive can easily be recovered almost without losing anything.If the ransomware encrypts the entire disk - even System32 and SysWOW64 - then you have a non-bootable, "black screen" system = not very effective for the malc0der in extracting $ from the system owner. If the malc0der is just plain mean, then such encryption would be one of the most malicious -- but why do that ? They can just wipe your entire drive -- which is a lot easier to code. A comparatively simple script can wipe a drive...
That wiped hard drive can easily be recovered almost without losing anything.
Thanks, would love to know more from research paper, would you please refer to any specific link for that?Deleted files can be recovered, but a digitally sanitized\wiped drive where all data is over-written with 0s and 1s cannot be recovered - at least not easily - and what can be recovered - is almost certainly worthless to the typical user.
Also, on SSDs deleted files are unrecoverable once the TRIM command is sent.
There's online research papers that discuss all this...
Thanks, would love to know more from research paper, would you please refer to any specific link for that?
Nice mention!Deleted files can be recovered, but a digitally sanitized\wiped drive where all data is over-written with 0s and 1s cannot be recovered - at least not easily - and what can be recovered - is almost certainly worthless to the typical user.
Also, on SSDs deleted files are unrecoverable once the TRIM command is sent.
There's online research papers that discuss all this...
Unluckily for us RSA encryption is not breakable as of now.. without knowing that key there's no decryption that fileUsually, the ransomware uses RSA
Glad someone mentioned the NTAPI as now I can magically make an addition to the file removal stuff above.. There's another API: ZwDeleteFile. This API can be used to remove a file even whilst it's being used by another process. Just a lower-level way of the normal removal.. Magic! Poof! - "Mum get the camera! where'd the file go off my documents? my program had it open! quick call the BBC news to come report this. someone just broke the Windows lawsThere are undocumented functions that take advantage of the API: ZwQuerySystemInformation to get all the open handles and ZwQueryInformationFile to obtain the name of the file according to the handle.
Well saidPetya inserts itself into the MBR and edit the boot loader present in it, replacing it with his and after it the figure MFT blocking access to the file because all the information related to the name of the file to the folder, permissions, modification dates, dimensions and their location on the disk (list of blocks or clusters that contain the files) are encrypted.
It seems that some new versions of Cryptolocker, while changing the mode of encryption and therefore making it much more difficult to the possible extraction of the keystream, seem to be vulnerable to cryptoanalysis attackUnluckily for us RSA encryption is not breakable as of now.. without knowing that key there's no decryption that file. Although sometimes we are lucky as for some malware devs don't know a lot and make mistakes when working with things like the CryptoAPI which leaves a hole to be abused by us ourselves and get some revenge by recovering the file without needing the key from them directly.. ha to their faces!
![]()
Hahaha! It's great when we catch them out and ruin their day when they find out they messed up and someone found their mistake and used it to make a decryption tool! And it makes the victims day better to know they were saved by a heroIt seems that some new versions of Cryptolocker, while changing the mode of encryption and therefore making it much more difficult to the possible extraction of the keystream, seem to be vulnerable to cryptoanalysis attack![]()