Analysis

  • max time kernel
    479s
  • max time network
    450s
  • platform
    windows11-21h2_x64
  • resource
    win11-20240221-en
  • resource tags

    arch:x64arch:x86image:win11-20240221-enlocale:en-usos:windows11-21h2-x64system
  • submitted
    11-03-2024 06:53

General

  • Target

    lockbit_v3_unpacked.exe

  • Size

    162KB

  • MD5

    628e4a77536859ffc2853005924db2ef

  • SHA1

    c2a321b6078acfab582a195c3eaf3fe05e095ce0

  • SHA256

    d61af007f6c792b8fb6c677143b7d0e2533394e28c50737588e40da475c040ee

  • SHA512

    aae3e3e9b12ab7389e5f2eac89b2a306c4d2b91bb4204f83cc7308a83c3dea88bbc2d826546c886fd580c01245a6be5c0aefcd93936daeecb3614935248de5f1

  • SSDEEP

    3072:o5uyulsHwDV1gFnTwn7zwJGJ+3t5kCI5Gzei3N2VzRmK:o5uZ1DPgFnk7EJwaI5gDN2VVm

Score
10/10

Malware Config

Extracted

Path

C:\Users\HLJkNskOq.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 Links for chat: 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: B30C8622DB53FF5955D91C603A5A2500 <<<<< >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> 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://lockbitsupa7e3b4pkn4mgkgojrl5iqgx24clbzc4xm7i6jeetsia3qd.onion

Signatures

  • Lockbit

    Ransomware family with multiple variants released since late 2019.

  • Rule to detect Lockbit 3.0 ransomware Windows payload 2 IoCs
  • 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
  • Enumerates physical storage devices 1 TTPs

    Attempts to interact with connected storage/optical drive(s).

  • 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 SetWindowsHookEx 13 IoCs
  • Suspicious use of WriteProcessMemory 11 IoCs

Processes

  • C:\Users\Admin\AppData\Local\Temp\lockbit_v3_unpacked.exe
    "C:\Users\Admin\AppData\Local\Temp\lockbit_v3_unpacked.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:4032
    • C:\Windows\splwow64.exe
      C:\Windows\splwow64.exe 12288
      2⤵
      • Drops file in System32 directory
      PID:1660
    • C:\ProgramData\801E.tmp
      "C:\ProgramData\801E.tmp"
      2⤵
      • Deletes itself
      • Executes dropped EXE
      • Suspicious use of NtSetInformationThreadHideFromDebugger
      • Suspicious behavior: RenamesItself
      • Suspicious use of WriteProcessMemory
      PID:3384
      • C:\Windows\SysWOW64\cmd.exe
        "C:\Windows\System32\cmd.exe" /C DEL /F /Q C:\PROGRA~3\801E.tmp >> NUL
        3⤵
          PID:4944
    • C:\Windows\system32\svchost.exe
      C:\Windows\system32\svchost.exe -k PrintWorkflow -s PrintWorkflowUserSvc
      1⤵
        PID:2744
      • C:\Windows\system32\printfilterpipelinesvc.exe
        C:\Windows\system32\printfilterpipelinesvc.exe -Embedding
        1⤵
        • Drops file in System32 directory
        • Suspicious use of WriteProcessMemory
        PID:3088
        • C:\Program Files\Microsoft Office\root\Office16\ONENOTE.EXE
          /insertdoc "C:\Users\Admin\AppData\Local\Microsoft\Windows\INetCache\{8308E22A-4214-4D90-AE36-EB04B283AE7A}.xps" 133546139364300000
          2⤵
          • Checks processor information in registry
          • Enumerates system info in registry
          • Suspicious behavior: EnumeratesProcesses
          • Suspicious use of SetWindowsHookEx
          PID:4636

      Network

      MITRE ATT&CK Enterprise v15

      Replay Monitor

      Loading Replay Monitor...

      Downloads

      • C:\$Recycle.Bin\S-1-5-21-4181651180-3163410697-3990547336-1000\VVVVVVVVVVV

        Filesize

        129B

        MD5

        2cd816983a79d70cbd55ae1f4f139b1a

        SHA1

        d7e07399d1126c09675533cc4a0b2fedda4c1509

        SHA256

        f8825714d2fbb2b82aec970113d0fed4cb996869b2b31dbdad176c99e08c4e64

        SHA512

        1032c009f0755bea89f008fe48587ddb660a438e46fb03bcfd6d48cdcca369b1a0c52d16fe3781705dd87fe591a47bccbabdc01b1d940ef5a680f4a6a2855c7b

      • C:\ProgramData\801E.tmp

        Filesize

        14KB

        MD5

        294e9f64cb1642dd89229fff0592856b

        SHA1

        97b148c27f3da29ba7b18d6aee8a0db9102f47c9

        SHA256

        917e115cc403e29b4388e0d175cbfac3e7e40ca1742299fbdb353847db2de7c2

        SHA512

        b87d531890bf1577b9b4af41dddb2cdbbfa164cf197bd5987df3a3075983645a3acba443e289b7bfd338422978a104f55298fbfe346872de0895bde44adc89cf

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

        Filesize

        162KB

        MD5

        772ea5172e1eec1a08dea97c413a1460

        SHA1

        7ce9008c5f35f924436d1d69cf66d8a42d105fa1

        SHA256

        8f6e5bc4bec802bf1487f928d8b6552ab5064311e6199418f1e33687d79d8c22

        SHA512

        283b76e6fa92fc655d17fc1ff510300215bbac69157c15bac9d38c7adc43767a6cb12d05c0c8ab2b878f4ce92b1bfe4feba2f8640c61b38ec1d0bc0734120534

      • C:\Users\Admin\AppData\Local\Temp\{81BD586D-AC3E-4A4A-BD84-4EFFFA806C5F}

        Filesize

        4KB

        MD5

        a9ef184a1eb5f94aa773f74279101a9e

        SHA1

        41f4fa4bb7224875866ef7e3144492d27ed345c9

        SHA256

        53691e0de5f6a2b3b09278ca19bd0be50d3b269d12b9d1c7574ab2a1ec061b13

        SHA512

        bfb676591479663e94093664e55a2944f736e819a84dcbe7310df250b5a590451c2451c4e25202dcba88a02d39a65ada59aa80b5559ed64797d5232c0df1d743

      • C:\Users\HLJkNskOq.README.txt

        Filesize

        10KB

        MD5

        3ee9ee4722b32213f37931bf5822eea1

        SHA1

        f53053c66b5f7ba6647020b783e6054c83ad8c8d

        SHA256

        6a50b003049e131dec77035495717177f9cc83e5f81b50a3d78b5ccee1bc38c7

        SHA512

        72df4d50b390fc824baf853d1cc32c4cd53136a7d3386ef07b78f4fec7676ea49b0af564992d07ed30e020b775b5ad32c9391caf73424e97d8aa19eced0bce01

      • F:\$RECYCLE.BIN\S-1-5-21-4181651180-3163410697-3990547336-1000\DDDDDDDDDDD

        Filesize

        129B

        MD5

        f34c8e850cec05528a7cff36dd9de114

        SHA1

        d6eb4ff81cf3d40cda9fbc1dcfb125d04ed1460e

        SHA256

        5545682bc760d381b9b476f73167763975f8c3e181b13fa5131ac6aaa667e700

        SHA512

        50c2be3f4a9ebcf51eaffedf39a8fabf8a0f0db4e2f9930151a8dc3969ea1439f557d2f8b108ee24c0c5685cbca3cdb2e44a42682f7de75e121bf73c39f38cdf

      • memory/3384-380-0x0000000002620000-0x0000000002630000-memory.dmp

        Filesize

        64KB

      • memory/3384-385-0x000000007FE30000-0x000000007FE31000-memory.dmp

        Filesize

        4KB

      • memory/3384-384-0x000000007FE10000-0x000000007FE11000-memory.dmp

        Filesize

        4KB

      • memory/3384-381-0x0000000002620000-0x0000000002630000-memory.dmp

        Filesize

        64KB

      • memory/3384-360-0x000000007FDF0000-0x000000007FDF1000-memory.dmp

        Filesize

        4KB

      • memory/3384-359-0x000000007FE50000-0x000000007FE51000-memory.dmp

        Filesize

        4KB

      • memory/3384-357-0x0000000002620000-0x0000000002630000-memory.dmp

        Filesize

        64KB

      • memory/3384-356-0x000000007FE70000-0x000000007FE71000-memory.dmp

        Filesize

        4KB

      • memory/4032-317-0x0000000000400000-0x000000000042C000-memory.dmp

        Filesize

        176KB

      • memory/4032-2-0x0000000002620000-0x0000000002630000-memory.dmp

        Filesize

        64KB

      • memory/4032-3-0x0000000002620000-0x0000000002630000-memory.dmp

        Filesize

        64KB

      • memory/4032-1-0x0000000002620000-0x0000000002630000-memory.dmp

        Filesize

        64KB

      • memory/4032-0-0x0000000000400000-0x000000000042C000-memory.dmp

        Filesize

        176KB

      • memory/4636-319-0x00007FF8365B0000-0x00007FF8365C0000-memory.dmp

        Filesize

        64KB

      • memory/4636-316-0x00007FF8365B0000-0x00007FF8365C0000-memory.dmp

        Filesize

        64KB

      • memory/4636-313-0x00007FF8365B0000-0x00007FF8365C0000-memory.dmp

        Filesize

        64KB

      • memory/4636-351-0x00007FF876520000-0x00007FF876729000-memory.dmp

        Filesize

        2.0MB

      • memory/4636-355-0x00007FF876520000-0x00007FF876729000-memory.dmp

        Filesize

        2.0MB

      • memory/4636-358-0x00007FF833A90000-0x00007FF833AA0000-memory.dmp

        Filesize

        64KB

      • memory/4636-354-0x00007FF876520000-0x00007FF876729000-memory.dmp

        Filesize

        2.0MB

      • memory/4636-352-0x00007FF8365B0000-0x00007FF8365C0000-memory.dmp

        Filesize

        64KB

      • memory/4636-362-0x00007FF833A90000-0x00007FF833AA0000-memory.dmp

        Filesize

        64KB

      • memory/4636-361-0x00007FF874850000-0x00007FF87490D000-memory.dmp

        Filesize

        756KB

      • memory/4636-353-0x00007FF876520000-0x00007FF876729000-memory.dmp

        Filesize

        2.0MB

      • memory/4636-379-0x00007FF876520000-0x00007FF876729000-memory.dmp

        Filesize

        2.0MB

      • memory/4636-350-0x00007FF876520000-0x00007FF876729000-memory.dmp

        Filesize

        2.0MB

      • memory/4636-349-0x00007FF8365B0000-0x00007FF8365C0000-memory.dmp

        Filesize

        64KB

      • memory/4636-382-0x00007FF874850000-0x00007FF87490D000-memory.dmp

        Filesize

        756KB

      • memory/4636-337-0x00007FF876520000-0x00007FF876729000-memory.dmp

        Filesize

        2.0MB

      • memory/4636-318-0x00007FF876520000-0x00007FF876729000-memory.dmp

        Filesize

        2.0MB