Just like EDA2 and new one WANNACRY(a little bit)
It is a good idea
That was interesting technique
What if I change the scenario: (Default)each victim machine has its own randomized key, then hash key with SHA then hashed data use as AES encryption key,[in default state, the key generated in this step will use to encrypt files](new scenario)encrypt AES output with public key[the final key generated], then use this to encrypt files
But as John Constantine said " always there is a catch "
So, if I use a fixed public key to encrypt files, when the first victim get private key to decrypt his/her files, it can share key in public and all others can decrypt their files
What can I do for this?
I have an idea, at the beginning of the program, the ransomware will send PC_name and USER_name to a server, the server will generate public/private key and will store both+victim details in its db and will send the public key to the victim.
I was thinking about another scenario.
How if I Encrypt files with public key?
Again, There is a catch. Here problem is file size
Because RSA encryption only works if the file size is lesser than the public modulus n. This is because while decrypting the file the modulus over n is applied to the encrypted file.
So, I think I should fragment files
(This is just a raw idea)
Hovov, It was finally over(I Think)