Skip to content

Instantly share code, notes, and snippets.

@hasherezade
Created July 5, 2017 19:57
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
Star You must be signed in to star a gist
Save hasherezade/7de547822c5e47d6fe39e35824fbb66c to your computer and use it in GitHub Desktop.
enter aes-256-cbc decryption password:
Congratulations!
Here is our secp192k1 privkey:
38dd46801ce61883433048d6d8c6ab8be18654a2695b4723
We used ECIES (with AES-256-ECB) Scheme to encrypt the decryption password into the "Personal Code" which is BASE58 encoded.
@hasherezade
Copy link
Author

hasherezade commented Jul 5, 2017

It seems that this is Janus' private key for all the previous Petyas. This key cannot help in case of EternalPetya, since, in this particular case, the Salsa keys are not encrypted with Janus' public key, but, instead of this, erased and lost forever. However, it can help to the people who were attacked by Petya/Goldeneye in the past. I will write a decryptor soon, stay tuned!

@hasherezade
Copy link
Author

The decryptor is ready. You can find it here: https://github.com/hasherezade/petya_key

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment