Jump to content

cybermetric

Member
  • Posts

    75
  • Joined

  • Days Won

    5

cybermetric last won the day on October 6 2021

cybermetric had the most liked content!

Reputation

12 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Fabio: This is NOT a newer version of STOP. The OP should submit an encrypted file and a ransom note to the IDR site here: https://id-ransomware.malwarehunterteam.com/ The site will attempt to identify the ransomware his files are actually encrypted with.
  2. Run the Emsisoft decrypter on some of your encrypted files every week or so to check. Emsisoft does not report key recoveries.
  3. Are you sure the extension is .qlda? There is a new STOP variant the extension .qdla (V0347)
  4. This is the .npsk STOP variant. Unfortunately, the offline/private key has never been donated to Emsisoft by a victim that paid the ransom and got the key.
  5. Are you sure it's 338? Another poster shows 337 for the version#. What is the complete ID shown in the ransom note?
  6. File pairs can only be used with the "old variant" STOP ransomware. The .tisc variant @Cyberguy has is a "new variant" version and cannot be decrypted by this method.
  7. Also, from the Emsisoft decrypter FAQ: Why won't the decrypter run? The decrypter requires version 4.5.2 or newer of the Microsoft .NET Framework, so this could mean your version of the .NET Framework is out of date. We recommend installing the latest version of the .NET Framework (4.8 at the time of writing this), and then trying the decrypter again. Make sure Windows has been completely updated.
  8. That has not ever happened for the STOP ransomware. Law enforcement has not nabbed the criminals and/or their servers.
  9. Both the .gujd and the ufwj STOP variants have the same offline ID (ends in "t1"). The same offline/private key will decrypt both variants if encrypted by the offline key, WHEN/IF Emsisoft is donated the offline/private key by a victim that has paid the ransom. This may or may not ever happen.
  10. You're right - it's .leex. This appears just above the decrypter log: Error: No key for New Variant offline ID: LTYv5JAYPKU9SqYbMp9sbHbkMoA4JlKc46dTaLt1Notice: this ID appears be an offline ID, decryption MAY be possible in the future. That is the offline ID for .leex.
  11. Something is amiss with the post of @Dinesh Shrestha. The first decrypter line indicates that he has an offline ID. Moreover, that is the offline ID for the .leek variant. The log from the decrypter indicates his files are encrypted by an online key of the .neer variant. 2 different encryptions? Or is the offline ID for the .neer variant the same as that for the .leek variant? I have no idea. Back to the experts!!
  12. The "error" is simply the decrypter's way of telling you that your files were encrypted by an online key, and cannot be decrypted. Simple as that.
×
×
  • Create New...