Ransomware Research

SecuredMe

SecuredMe was first discovered in February 2024 in enterprise cloud environments. SecuredMe is found in environments with a number of different names, including ShellLocker 2024, Dragon434, etc. For a full list of all names, please see below.

Name

SecuredMe

 

First Seen

February 2024

Targeting

Behavior of SecuredMe

SecuredMe is known to target specific file types. Below are all known file types that SecuredMe is known to infect.

In some cases, ransomware will update the modified date, when it encrypts files. SecuredMe updates the last modified date of the file it targets.

Details

Characteristics of SecuredMe

Suffixes

Some ransomware will change or append a suffix to the end of the file after they are encrypted, including changing the extension of a file. Here are some of the possible suffixes that SecuredMe ransomware is known to change.

Suffixes

.L0cked

Ransomware Notes

Not all ransomware leaves a note. However, some ransomware leaves the infected party instructions on what the user should do to get rid of the ransomware, or satisfy the ransom. This often involves transferring money, often bitcoin or another cryptocurrency to a designated wallet.

Below are the type(s) of notes, content, and typical locations where Elastio has found ransom notes from SecuredMe.

Type

File Name

Location

message

Login

Executables

These are the names of the executables that contain the undetonated ransomware payload for SecuredMe.

Executables

lock.exe, 501.exe, 501.bin, svchost.exe

External Pages

Ransomware often links to external pages such as payment pages, telegram contacts, etc. Below are some of the URLs Elastio has found to be associated with SecuredMe.

External Pages

  • http://dragon434pnhqvzhv764bzsguroslimv4kpwtt5gp55dsg53stnoumid.onion
  • mailto:securedme@dnmx.org

elastio-icon
Elastio Can Help You

Don’t let ransomware
take over your data.