Resubmissions

30-01-2024 16:24

240130-twf5hahfb4 10

30-01-2024 15:58

240130-tervnshea7 10

Analysis

  • max time kernel
    162s
  • max time network
    171s
  • platform
    windows10-1703_x64
  • resource
    win10-20231215-en
  • resource tags

    arch:x64arch:x86image:win10-20231215-enlocale:en-usos:windows10-1703-x64system
  • submitted
    30-01-2024 16:24

General

  • Target

    lockbit_1.exe

  • Size

    160KB

  • MD5

    fdd9f9ae1d24dcc709cd0abcea638ed0

  • SHA1

    2fe29b620b51d2258373b12d926a91d0a3720a60

  • SHA256

    4134d5d8f7b038e23e7887db56bb3ad295341a1aaf0bebe6be21d901d06dd662

  • SHA512

    db995ac8fa51a49e3b9550b0bb4069bbef08a9157d942cffcae24cabb720be01e17afffc9bfb54e95d4883adc6af27c5cb78291d408d0137591eff690669c3ef

  • SSDEEP

    3072:5uJ9OlKolUa1U197bzhVsmftsoo4jE8AI8vOMvjEF0Q:5ufj0zi1dNVsmfttjY8LLej40Q

Score
10/10

Malware Config

Extracted

Path

C:\uQK11TJ9E.README.txt

Family

lockbit

Ransom Note
~~~ LockBit 3.0 the world's fastest and most stable ransomware from 2019~~~ >>>>> Your data is stolen and encrypted. If you don't pay the ransom, the data will be published on our TOR darknet sites. Keep in mind that once your data appears on our leak site, it could be bought by your competitors at any second, so don't hesitate for a long time. The sooner you pay the ransom, the sooner your company will be safe. Tor Browser Links: http://lockbitapt2d73krlbewgv27tquljgxr33xbwwsp6rkyieto7u4ncead.onion http://lockbitapt2yfbt7lchxejug47kmqvqqxvvjpqkmevv4l3azl3gy6pyd.onion http://lockbitapt34kvrip6xojylohhxrwsvpzdffgs5z4pbbsywnzsbdguqd.onion http://lockbitapt5x4zkjbcqmz6frdhecqqgadevyiwqxukksspnlidyvd7qd.onion http://lockbitapt6vx57t3eeqjofwgcglmutr3a35nygvokja5uuccip4ykyd.onion http://lockbitapt72iw55njgnqpymggskg5yp75ry7rirtdg4m7i42artsbqd.onion http://lockbitaptawjl6udhpd323uehekiyatj6ftcxmkwe5sezs4fqgpjpid.onion http://lockbitaptbdiajqtplcrigzgdjprwugkkut63nbvy2d5r4w2agyekqd.onion http://lockbitaptc2iq4atewz2ise62q63wfktyrl4qtwuk5qax262kgtzjqd.onion Links for normal browser: http://lockbitapt2d73krlbewgv27tquljgxr33xbwwsp6rkyieto7u4ncead.onion.ly http://lockbitapt2yfbt7lchxejug47kmqvqqxvvjpqkmevv4l3azl3gy6pyd.onion.ly http://lockbitapt34kvrip6xojylohhxrwsvpzdffgs5z4pbbsywnzsbdguqd.onion.ly http://lockbitapt5x4zkjbcqmz6frdhecqqgadevyiwqxukksspnlidyvd7qd.onion.ly http://lockbitapt6vx57t3eeqjofwgcglmutr3a35nygvokja5uuccip4ykyd.onion.ly http://lockbitapt72iw55njgnqpymggskg5yp75ry7rirtdg4m7i42artsbqd.onion.ly http://lockbitaptawjl6udhpd323uehekiyatj6ftcxmkwe5sezs4fqgpjpid.onion.ly http://lockbitaptbdiajqtplcrigzgdjprwugkkut63nbvy2d5r4w2agyekqd.onion.ly http://lockbitaptc2iq4atewz2ise62q63wfktyrl4qtwuk5qax262kgtzjqd.onion.ly >>>>> What guarantee is there that we won't cheat you? We are the oldest ransomware affiliate program on the planet, nothing is more important than our reputation. We are not a politically motivated group and we want nothing more than money. If you pay, we will provide you with decryption software and destroy the stolen data. After you pay the ransom, you will quickly make even more money. Treat this situation simply as a paid training for your system administrators, because it is due to your corporate network not being properly configured that we were able to attack you. Our pentest services should be paid just like you pay the salaries of your system administrators. Get over it and pay for it. If we don't give you a decryptor or delete your data after you pay, no one will pay us in the future. You can get more information about us on Ilon Musk's Twitter https://twitter.com/hashtag/lockbit?f=live >>>>> You need to contact us and decrypt one file for free on TOR darknet sites with your personal ID Download and install Tor Browser https://www.torproject.org/ Write to the chat room and wait for an answer, we'll guarantee a response from you. If you need a unique ID for correspondence with us that no one will know about, tell it in the chat, we will generate a secret chat for you and give you his ID via private one-time memos service, no one can find out this ID but you. Sometimes you will have to wait some time for our reply, this is because we have a lot of work and we attack hundreds of companies around the world. Tor Browser personal link available only to you (available during a ddos attack): http://lockbitsupo7vv5vcl3jxpsdviopwvasljqcstym6efhh6oze7c6xjad.onion Tor Browser Links for chat (sometimes unavailable due to ddos attacks): http://lockbitsupa7e3b4pkn4mgkgojrl5iqgx24clbzc4xm7i6jeetsia3qd.onion http://lockbitsupdwon76nzykzblcplixwts4n4zoecugz2bxabtapqvmzqqd.onion http://lockbitsupn2h6be2cnqpvncyhj4rgmnwn44633hnzzmtxdvjoqlp7yd.onion http://lockbitsupo7vv5vcl3jxpsdviopwvasljqcstym6efhh6oze7c6xjad.onion http://lockbitsupq3g62dni2f36snrdb4n5qzqvovbtkt5xffw3draxk6gwqd.onion http://lockbitsupqfyacidr6upt6nhhyipujvaablubuevxj6xy3frthvr3yd.onion http://lockbitsupt7nr3fa6e7xyb73lk6bw6rcneqhoyblniiabj4uwvzapqd.onion http://lockbitsupuhswh4izvoucoxsbnotkmgq6durg7kficg6u33zfvq3oyd.onion http://lockbitsupxcjntihbmat4rrh7ktowips2qzywh6zer5r3xafhviyhqd.onion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> Your personal ID: 399ADB7062B0C994F47E7B8C39A6423E <<<<< >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> Warning! Do not delete or modify encrypted files, it will lead to problems with decryption of files! >>>>> Don't go to the police or the FBI for help and don't tell anyone that we attacked you. They won't help and will only make things worse for you. In 3 years not a single member of our group has been caught by the police, we are top notch hackers and we never leave a trail of crime. The police will try to prohibit you from paying the ransom in any way. The first thing they will tell you is that there is no guarantee to decrypt your files and remove stolen files, this is not true, we can do a test decryption before paying and your data will be guaranteed to be removed because it is a matter of our reputation, we make hundreds of millions of dollars and are not going to lose our revenue because of your files. It is very beneficial for the police and FBI to let everyone on the planet know about your data leak because then your state will get the fines budgeted for you due to GDPR and other similar laws. The fines will be used to fund the police and the FBI, they will eat more sweet coffee donuts and get fatter and fatter. The police and the FBI don't care what losses you suffer as a result of our attack, and we will help you get rid of all your problems for a modest sum of money. Along with this you should know that it is not necessarily your company that has to pay the ransom and not necessarily from your bank account, it can be done by an unidentified person, such as any philanthropist who loves your company, for example, Elon Musk, so the police will not do anything to you if someone pays the ransom for you. If you're worried that someone will trace your bank transfers, you can easily buy cryptocurrency for cash, thus leaving no digital trail that someone from your company paid our ransom. The police and FBI will not be able to stop lawsuits from your customers for leaking personal and private information. The police and FBI will not protect you from repeated attacks. Paying the ransom to us is much cheaper and more profitable than paying fines and legal fees. >>>>> What are the dangers of leaking your company's data. First of all, you will receive fines from the government such as the GDRP and many others, you can be sued by customers of your firm for leaking information that was confidential. Your leaked data will be used by all the hackers on the planet for various unpleasant things. For example, social engineering, your employees' personal data can be used to re-infiltrate your company. Bank details and passports can be used to create bank accounts and online wallets through which criminal money will be laundered. On another vacation trip, you will have to explain to the FBI where you got millions of dollars worth of stolen cryptocurrency transferred through your accounts on cryptocurrency exchanges. Your personal information could be used to make loans or buy appliances. You would later have to prove in court that it wasn't you who took out the loan and pay off someone else's loan. Your competitors may use the stolen information to steal technology or to improve their processes, your working methods, suppliers, investors, sponsors, employees, it will all be in the public domain. You won't be happy if your competitors lure your employees to other firms offering better wages, will you? Your competitors will use your information against you. For example, look for tax violations in the financial documents or any other violations, so you have to close your firm. According to statistics, two thirds of small and medium-sized companies close within half a year after a data breach. You will have to find and fix the vulnerabilities in your network, work with the customers affected by data leaks. All of these are very costly procedures that can exceed the cost of a ransomware buyout by a factor of hundreds. It's much easier, cheaper and faster to pay us the ransom. Well and most importantly, you will suffer a reputational loss, you have been building your company for many years, and now your reputation will be destroyed. Read more about the GDRP legislation:: https://en.wikipedia.org/wiki/General_Data_Protection_Regulation https://gdpr.eu/what-is-gdpr/ https://gdpr-info.eu/ >>>>> Don't go to recovery companies, they are essentially just middlemen who will make money off you and cheat you. We are well aware of cases where recovery companies tell you that the ransom price is 5 million dollars, but in fact they secretly negotiate with us for 1 million dollars, so they earn 4 million dollars from you. If you approached us directly without intermediaries you would pay 5 times less, that is 1 million dollars. >>>> Very important! For those who have cyber insurance against ransomware attacks. Insurance companies require you to keep your insurance information secret, this is to never pay the maximum amount specified in the contract or to pay nothing at all, disrupting negotiations. The insurance company will try to derail negotiations in any way they can so that they can later argue that you will be denied coverage because your insurance does not cover the ransom amount. For example your company is insured for 10 million dollars, while negotiating with your insurance agent about the ransom he will offer us the lowest possible amount, for example 100 thousand dollars, we will refuse the paltry amount and ask for example the amount of 15 million dollars, the insurance agent will never offer us the top threshold of your insurance of 10 million dollars. He will do anything to derail negotiations and refuse to pay us out completely and leave you alone with your problem. If you told us anonymously that your company was insured for $10 million and other important details regarding insurance coverage, we would not demand more than $10 million in correspondence with the insurance agent. That way you would have avoided a leak and decrypted your information. But since the sneaky insurance agent purposely negotiates so as not to pay for the insurance claim, only the insurance company wins in this situation. To avoid all this and get the money on the insurance, be sure to inform us anonymously about the availability and terms of insurance coverage, it benefits both you and us, but it does not benefit the insurance company. Poor multimillionaire insurers will not starve and will not become poorer from the payment of the maximum amount specified in the contract, because everyone knows that the contract is more expensive than money, so let them fulfill the conditions prescribed in your insurance contract, thanks to our interaction. >>>>> If you do not pay the ransom, we will attack your company again in the future.
URLs

http://lockbitapt2d73krlbewgv27tquljgxr33xbwwsp6rkyieto7u4ncead.onion

http://lockbitapt2yfbt7lchxejug47kmqvqqxvvjpqkmevv4l3azl3gy6pyd.onion

http://lockbitapt34kvrip6xojylohhxrwsvpzdffgs5z4pbbsywnzsbdguqd.onion

http://lockbitapt5x4zkjbcqmz6frdhecqqgadevyiwqxukksspnlidyvd7qd.onion

http://lockbitapt6vx57t3eeqjofwgcglmutr3a35nygvokja5uuccip4ykyd.onion

http://lockbitapt72iw55njgnqpymggskg5yp75ry7rirtdg4m7i42artsbqd.onion

http://lockbitaptawjl6udhpd323uehekiyatj6ftcxmkwe5sezs4fqgpjpid.onion

http://lockbitaptbdiajqtplcrigzgdjprwugkkut63nbvy2d5r4w2agyekqd.onion

http://lockbitaptc2iq4atewz2ise62q63wfktyrl4qtwuk5qax262kgtzjqd.onion

http://lockbitapt2d73krlbewgv27tquljgxr33xbwwsp6rkyieto7u4ncead.onion.ly

http://lockbitapt2yfbt7lchxejug47kmqvqqxvvjpqkmevv4l3azl3gy6pyd.onion.ly

http://lockbitapt34kvrip6xojylohhxrwsvpzdffgs5z4pbbsywnzsbdguqd.onion.ly

http://lockbitapt5x4zkjbcqmz6frdhecqqgadevyiwqxukksspnlidyvd7qd.onion.ly

http://lockbitapt6vx57t3eeqjofwgcglmutr3a35nygvokja5uuccip4ykyd.onion.ly

http://lockbitapt72iw55njgnqpymggskg5yp75ry7rirtdg4m7i42artsbqd.onion.ly

http://lockbitaptawjl6udhpd323uehekiyatj6ftcxmkwe5sezs4fqgpjpid.onion.ly

http://lockbitaptbdiajqtplcrigzgdjprwugkkut63nbvy2d5r4w2agyekqd.onion.ly

http://lockbitaptc2iq4atewz2ise62q63wfktyrl4qtwuk5qax262kgtzjqd.onion.ly

https://twitter.com/hashtag/lockbit?f=live

http://lockbitsupo7vv5vcl3jxpsdviopwvasljqcstym6efhh6oze7c6xjad.onion

Signatures

  • Lockbit

    Ransomware family with multiple variants released since late 2019.

  • Deletes itself 1 IoCs
  • Executes dropped EXE 1 IoCs
  • Drops desktop.ini file(s) 2 IoCs
  • Drops file in System32 directory 4 IoCs
  • Sets desktop wallpaper using registry 2 TTPs 2 IoCs
  • Suspicious use of NtSetInformationThreadHideFromDebugger 12 IoCs
  • Checks processor information in registry 2 TTPs 3 IoCs

    Processor information is often read in order to detect sandboxing environments.

  • Enumerates system info in registry 2 TTPs 3 IoCs
  • Modifies Control Panel 2 IoCs
  • Modifies registry class 5 IoCs
  • Suspicious behavior: EnumeratesProcesses 14 IoCs
  • Suspicious behavior: RenamesItself 26 IoCs
  • Suspicious use of AdjustPrivilegeToken 64 IoCs
  • Suspicious use of FindShellTrayWindow 1 IoCs
  • Suspicious use of SetWindowsHookEx 14 IoCs
  • Suspicious use of WriteProcessMemory 8 IoCs

Processes

  • C:\Users\Admin\AppData\Local\Temp\lockbit_1.exe
    "C:\Users\Admin\AppData\Local\Temp\lockbit_1.exe"
    1⤵
    • Drops desktop.ini file(s)
    • Sets desktop wallpaper using registry
    • Suspicious use of NtSetInformationThreadHideFromDebugger
    • Modifies Control Panel
    • Modifies registry class
    • Suspicious behavior: EnumeratesProcesses
    • Suspicious use of AdjustPrivilegeToken
    • Suspicious use of WriteProcessMemory
    PID:576
    • C:\Windows\splwow64.exe
      C:\Windows\splwow64.exe 12288
      2⤵
      • Drops file in System32 directory
      PID:2608
    • C:\ProgramData\38DF.tmp
      "C:\ProgramData\38DF.tmp"
      2⤵
      • Deletes itself
      • Executes dropped EXE
      • Suspicious use of NtSetInformationThreadHideFromDebugger
      • Suspicious behavior: RenamesItself
      PID:3524
  • C:\Windows\system32\printfilterpipelinesvc.exe
    C:\Windows\system32\printfilterpipelinesvc.exe -Embedding
    1⤵
    • Drops file in System32 directory
    • Suspicious use of WriteProcessMemory
    PID:4788
    • C:\Program Files\Microsoft Office\root\Office16\ONENOTE.EXE
      /insertdoc "C:\Users\Admin\AppData\Local\Microsoft\Windows\INetCache\{91E8818A-21ED-4D2C-82C2-9D31C0D1E7FB}.xps" 133511054931360000
      2⤵
      • Checks processor information in registry
      • Enumerates system info in registry
      • Suspicious behavior: EnumeratesProcesses
      • Suspicious use of FindShellTrayWindow
      • Suspicious use of SetWindowsHookEx
      PID:3812

Network

MITRE ATT&CK Enterprise v15

Replay Monitor

Loading Replay Monitor...

Downloads

  • C:\$Recycle.Bin\S-1-5-21-1682406436-2801920780-981986064-1000\YYYYYYYYYYY

    Filesize

    129B

    MD5

    101cf49eb0f732ac8ba17d12c32ae4f2

    SHA1

    3e4f5b8b77716204722656f2df15565422802597

    SHA256

    e0773fc971c17e277770d328c399a371f6d97b4756c01fc2235201272b2fdcf0

    SHA512

    376ad7502764cbf9791717544ba0faecc115da4f89c18acadd3347b014a2b0e57a203e400182f62632807a5485b9334a7ec5054d75aa0a62018dc2757099dda1

  • C:\ProgramData\38DF.tmp

    Filesize

    14KB

    MD5

    294e9f64cb1642dd89229fff0592856b

    SHA1

    97b148c27f3da29ba7b18d6aee8a0db9102f47c9

    SHA256

    917e115cc403e29b4388e0d175cbfac3e7e40ca1742299fbdb353847db2de7c2

    SHA512

    b87d531890bf1577b9b4af41dddb2cdbbfa164cf197bd5987df3a3075983645a3acba443e289b7bfd338422978a104f55298fbfe346872de0895bde44adc89cf

  • C:\Users\Admin\AppData\Local\Microsoft\Windows\INetCache\{91E8818A-21ED-4D2C-82C2-9D31C0D1E7FB}.xps

    Filesize

    9.1MB

    MD5

    8800a17d7d518e13789fb9b0074e157f

    SHA1

    d4a581a839a982ace1bc96a475088c593aca1505

    SHA256

    3bd9a17c6feb95a062287b3adbbb4db91a3a5142bd5402c7c4e155224d454bb8

    SHA512

    0039323ccedfac0006171ac77f7592c92a92fc199cc11721cd2b3153a0587513a5ee14c8388bddebb8928a42cf3ae2a6bbaef0eb58f6ba127895fa0eea775481

  • C:\Users\Admin\AppData\Local\Temp\DDDDDDDDDDDDD

    Filesize

    160KB

    MD5

    a920b5fc659d14b8c2f078da2253274f

    SHA1

    7f424c205dd5a8abe38fc693ef7552163a14b10b

    SHA256

    21680b358f6cc786587cdf8d333f5a55e8366f887ba771388e90c8ef5b43f699

    SHA512

    84640f45ff502a8b4f150747327ecad611fd0b8ddc5f03fef34f4fe711ab211a2ffe57e0460ada2d885cb889096d2cc5c2521a55c7f0308b26f9afcd06c87349

  • C:\uQK11TJ9E.README.txt

    Filesize

    10KB

    MD5

    5bf90e79772a2ac636743bfd5424d06e

    SHA1

    954f2388df2f17b52a2fdf1f036e44acb0c4485c

    SHA256

    8bff2e8d1504abc571aeb6c7ba26fb0cc85df0ded8d7d9b2c7cde39ab8e85cd2

    SHA512

    e5a6d03f824fe3f8c79af9242d849a6506d1641829ce44dd139a2fb9e791fa96d64aad8ff7f56e096ba42fe0ff7f516f6c25a5ae3f2f503151b45e5c3d201200

  • F:\$RECYCLE.BIN\S-1-5-21-1682406436-2801920780-981986064-1000\DDDDDDDDDDD

    Filesize

    129B

    MD5

    6a7133e10bb6df233c693ca396687bc5

    SHA1

    0f5c239e90b03425b06a245fcbf2c3529a36a2fd

    SHA256

    6521167b11e13725086de333bb3855fd5c742adffbfcf0834977f29daaf9089c

    SHA512

    9f7c7711b061ba7685f8f238d9ef7239b2dbbee0dbc638893ade6a8d15a39d0d44643eb33d1e3ddfeddacef40e9ff63aad8bd7e82e76e8657d312290c2b8d7a4

  • memory/576-311-0x00000000023A0000-0x00000000023B0000-memory.dmp

    Filesize

    64KB

  • memory/576-0-0x00000000023A0000-0x00000000023B0000-memory.dmp

    Filesize

    64KB

  • memory/576-310-0x00000000023A0000-0x00000000023B0000-memory.dmp

    Filesize

    64KB

  • memory/576-1-0x00000000023A0000-0x00000000023B0000-memory.dmp

    Filesize

    64KB

  • memory/576-2-0x00000000023A0000-0x00000000023B0000-memory.dmp

    Filesize

    64KB

  • memory/3524-774-0x0000000002650000-0x0000000002660000-memory.dmp

    Filesize

    64KB

  • memory/3524-773-0x0000000002650000-0x0000000002660000-memory.dmp

    Filesize

    64KB

  • memory/3524-364-0x000000007FEA0000-0x000000007FEA1000-memory.dmp

    Filesize

    4KB

  • memory/3524-344-0x0000000002650000-0x0000000002660000-memory.dmp

    Filesize

    64KB

  • memory/3524-345-0x0000000002650000-0x0000000002660000-memory.dmp

    Filesize

    64KB

  • memory/3524-349-0x000000007FE20000-0x000000007FE21000-memory.dmp

    Filesize

    4KB

  • memory/3524-348-0x000000007FE80000-0x000000007FE81000-memory.dmp

    Filesize

    4KB

  • memory/3812-343-0x00007FFE38A50000-0x00007FFE38A60000-memory.dmp

    Filesize

    64KB

  • memory/3812-360-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-353-0x00007FFE776F0000-0x00007FFE7779E000-memory.dmp

    Filesize

    696KB

  • memory/3812-354-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-352-0x00007FFE35070000-0x00007FFE35080000-memory.dmp

    Filesize

    64KB

  • memory/3812-351-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-355-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-358-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-357-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-356-0x00007FFE35070000-0x00007FFE35080000-memory.dmp

    Filesize

    64KB

  • memory/3812-359-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-350-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-362-0x00007FFE776F0000-0x00007FFE7779E000-memory.dmp

    Filesize

    696KB

  • memory/3812-308-0x00007FFE38A50000-0x00007FFE38A60000-memory.dmp

    Filesize

    64KB

  • memory/3812-366-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-768-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-342-0x00007FFE38A50000-0x00007FFE38A60000-memory.dmp

    Filesize

    64KB

  • memory/3812-770-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-337-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB

  • memory/3812-312-0x00007FFE38A50000-0x00007FFE38A60000-memory.dmp

    Filesize

    64KB

  • memory/3812-778-0x00007FFE789C0000-0x00007FFE78B9B000-memory.dmp

    Filesize

    1.9MB