Analysis
- max time kernel
153s - max time network
155s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
15/03/2024, 04:46
Behavioral task
behavioral1
Sample
2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe
Resource
win10v2004-20240226-en
General
- Target 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe
- Size 162KB
- Sample240315-fd23csge5t
- SHA256 1f9944ccc4cb956c4eb81e76d51b3cb048b838f2f746e2017d4492abd5e9ed79
- MD5 a2bc2785420b0c6f685d8692d813fbbc
- SHA1 b118551289c9398a339cd1161b2c101571d4b5fd
- SHA512 32deb1d43a25b1b184f5ac212099d3004277d609d2784297c96632abe181e8c95f62185ea23ecefe640153c454bbcb33ef879d6c2d543f186160c9765e8bf0f8
- SSDEEP 3072:W5uyulsHwDV1gFnTwn7zwJGJ+at5kCI5Gzei3N2VzRmK:W5uZ1DPgFnk7EJwJI5gDN2VVm
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Extracted
-
C:\Users\HLJkNskOq.README.txt
-
lockbit
- ~~~ 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: B30C8622DB53FF595D3EB194354F39D4 <<<<< >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> 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.
-
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
-
http://lockbitsupdwon76nzykzblcplixwts4n4zoecugz2bxabtapqvmzqqd.onion
-
http://lockbitsupn2h6be2cnqpvncyhj4rgmnwn44633hnzzmtxdvjoqlp7yd.onion
-
http://lockbitsupo7vv5vcl3jxpsdviopwvasljqcstym6efhh6oze7c6xjad.onion
-
http://lockbitsupq3g62dni2f36snrdb4n5qzqvovbtkt5xffw3draxk6gwqd.onion
-
http://lockbitsupqfyacidr6upt6nhhyipujvaablubuevxj6xy3frthvr3yd.onion
-
http://lockbitsupt7nr3fa6e7xyb73lk6bw6rcneqhoyblniiabj4uwvzapqd.onion
-
http://lockbitsupuhswh4izvoucoxsbnotkmgq6durg7kficg6u33zfvq3oyd.onion
-
http://lockbitsupxcjntihbmat4rrh7ktowips2qzywh6zer5r3xafhviyhqd.onion
-
https://gdpr.eu/what-is-gdpr/
-
https://gdpr-info.eu/
Signatures
- Lockbit
Ransomware family with multiple variants released since late 2019.
- Rule to detect Lockbit 3.0 ransomware Windows payload 2 IoCs
resource yara_rule behavioral2/memory/3132-0-0x0000000000400000-0x000000000042C000-memory.dmp family_lockbit behavioral2/memory/3132-317-0x0000000000400000-0x000000000042C000-memory.dmp family_lockbit - Deletes itself 1 IoCs
pid Process 4972 9E20.tmp - Executes dropped EXE 1 IoCs
pid Process 4972 9E20.tmp - Drops desktop.ini file(s) 2 IoCs
description ioc Process File opened for modification C:\$Recycle.Bin\S-1-5-21-3808065738-1666277613-1125846146-1000\desktop.ini 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe File opened for modification F:\$RECYCLE.BIN\S-1-5-21-3808065738-1666277613-1125846146-1000\desktop.ini 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe - Drops file in System32 directory 4 IoCs
description ioc Process File created C:\Windows\system32\spool\PRINTERS\PPxu0a7w0g8xcizc4pfpbow30_.TMP printfilterpipelinesvc.exe File created C:\Windows\system32\spool\PRINTERS\00002.SPL splwow64.exe File created C:\Windows\system32\spool\PRINTERS\PP4k5hz29zm4qzd15g9rm0z51gb.TMP printfilterpipelinesvc.exe File created C:\Windows\system32\spool\PRINTERS\PP280uimlo0mym3mxumiwy1emk.TMP printfilterpipelinesvc.exe - Sets desktop wallpaper using registry 2 TTPs 2 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-3808065738-1666277613-1125846146-1000\Control Panel\Desktop\WallPaper = "C:\\ProgramData\\HLJkNskOq.bmp" 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Set value (str) \REGISTRY\USER\S-1-5-21-3808065738-1666277613-1125846146-1000\Control Panel\Desktop\Wallpaper = "C:\\ProgramData\\HLJkNskOq.bmp" 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe - Suspicious use of NtSetInformationThreadHideFromDebugger 12 IoCs
pid Process 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp - Checks processor information in registry 2 TTPs 3 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\Hardware\Description\System\CentralProcessor\0 ONENOTE.EXE Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\~MHz ONENOTE.EXE Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString ONENOTE.EXE - Enumerates system info in registry 2 TTPs 3 IoCs
description ioc Process Key opened \REGISTRY\MACHINE\Hardware\Description\System\BIOS ONENOTE.EXE Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemFamily ONENOTE.EXE Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemSKU ONENOTE.EXE - Modifies Control Panel 2 IoCs
description ioc Process Key created \REGISTRY\USER\S-1-5-21-3808065738-1666277613-1125846146-1000\Control Panel\Desktop 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Set value (str) \REGISTRY\USER\S-1-5-21-3808065738-1666277613-1125846146-1000\Control Panel\Desktop\WallpaperStyle = "10" 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe - Modifies registry class 5 IoCs
description ioc Process Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\HLJkNskOq\DefaultIcon\ = "C:\\ProgramData\\HLJkNskOq.ico" 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Key created \REGISTRY\MACHINE\SOFTWARE\Classes\.HLJkNskOq 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\.HLJkNskOq\ = "HLJkNskOq" 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Key created \REGISTRY\MACHINE\SOFTWARE\Classes\HLJkNskOq\DefaultIcon 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Key created \REGISTRY\MACHINE\SOFTWARE\Classes\HLJkNskOq 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe - Suspicious behavior: EnumeratesProcesses 16 IoCs
pid Process 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 3736 ONENOTE.EXE 3736 ONENOTE.EXE - Suspicious behavior: RenamesItself 26 IoCs
pid Process 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp 4972 9E20.tmp - Suspicious use of AdjustPrivilegeToken 64 IoCs
description pid Process Token: SeAssignPrimaryTokenPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeDebugPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: 36 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeImpersonatePrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeIncBasePriorityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeIncreaseQuotaPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: 33 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeManageVolumePrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeProfSingleProcessPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeRestorePrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSystemProfilePrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeTakeOwnershipPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeShutdownPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeDebugPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeBackupPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe Token: SeSecurityPrivilege 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe - Suspicious use of SetWindowsHookEx 13 IoCs
pid Process 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE 3736 ONENOTE.EXE - Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 3132 wrote to memory of 1164 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 109 PID 3132 wrote to memory of 1164 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 109 PID 4684 wrote to memory of 3736 4684 printfilterpipelinesvc.exe 114 PID 4684 wrote to memory of 3736 4684 printfilterpipelinesvc.exe 114 PID 3132 wrote to memory of 4972 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 115 PID 3132 wrote to memory of 4972 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 115 PID 3132 wrote to memory of 4972 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 115 PID 3132 wrote to memory of 4972 3132 2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe 115
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.exe"C:\Users\Admin\AppData\Local\Temp\2024-03-15_a2bc2785420b0c6f685d8692d813fbbc_darkside_lockbit.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:3132 -
C:\Windows\splwow64.exeC:\Windows\splwow64.exe 122882⤵
- Drops file in System32 directory
PID:1164
-
-
C:\ProgramData\9E20.tmp"C:\ProgramData\9E20.tmp"2⤵
- Deletes itself
- Executes dropped EXE
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Suspicious behavior: RenamesItself
PID:4972
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k PrintWorkflow -s PrintWorkflowUserSvc1⤵PID:4400
-
C:\Windows\system32\printfilterpipelinesvc.exeC:\Windows\system32\printfilterpipelinesvc.exe -Embedding1⤵
- Drops file in System32 directory
- Suspicious use of WriteProcessMemory
PID:4684 -
C:\Program Files\Microsoft Office\root\Office16\ONENOTE.EXE/insertdoc "C:\Users\Admin\AppData\Local\Microsoft\Windows\INetCache\{9BDB832D-345D-484B-9442-9022837B673A}.xps" 1335495161419000002⤵
- Checks processor information in registry
- Enumerates system info in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
PID:3736
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --mojo-platform-channel-handle=4068 --field-trial-handle=2900,i,14549994492153927475,12895178890800740987,262144 --variations-seed-version /prefetch:81⤵PID:3064
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
- Path C:\$Recycle.Bin\S-1-5-21-3808065738-1666277613-1125846146-1000\FFFFFFFFFFF
- Size 129B
- SHA256 e843dfb50c2bb8e0ce239a608ff7e540ad2912ad673203f171b98d1f4abdcea3
- MD5 763634f5e670b8fc8c24bdd4ece9047f
- SHA1 f2750ad02e1a972cf7d1e2e2b06e991db0b43e78
- SHA512 02c2be5720a87fa396d239d0d50cec7d9d05ef95e16663c87716758c42ce5a38562deea19b6d302b8396387e76de9fc058063e65c20e72b2da7964a2f32b7a38
- MD5 SHA1 SHA512
- Path C:\ProgramData\9E20.tmp
- Size 14KB
- SHA256 917e115cc403e29b4388e0d175cbfac3e7e40ca1742299fbdb353847db2de7c2
- MD5 294e9f64cb1642dd89229fff0592856b
- SHA1 97b148c27f3da29ba7b18d6aee8a0db9102f47c9
- SHA512 b87d531890bf1577b9b4af41dddb2cdbbfa164cf197bd5987df3a3075983645a3acba443e289b7bfd338422978a104f55298fbfe346872de0895bde44adc89cf
- SSDEEP 384:5cFP7VtpK4p+31Mzh79W5vM+ZyUgGq4BtMvAxXCRsi:A7Vf9p+qQ02y5HW6kX
- MD5 SHA1 SHA512 SSDEEP
- Path C:\Users\Admin\AppData\Local\Temp\DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
- Size 162KB
- SHA256 07f6aa39ec3ab4d20368605ed75addea2f800af4664a9c68ec4baebafc509250
- MD5 904be5114c3b8d55805807ab3e784d50
- SHA1 fe49040f4789403a75f194002b5e6db2312e9b12
- SHA512 e6a34fd02ea122593d4e36d3f7f339ac50b95dbf32bbf8e1dfe118f99dec3a170a22ef6afe1267663876a9baf7a23b97742eb1b655757cfe6731528d8f594943
- SSDEEP 3072:DUhI/3LLpyouatRDUhI/3LLpyouatRDUhI/3LLpK:YhIvfp2EYhIvfp2EYhIvfpK
- MD5 SHA1 SHA512 SSDEEP
- Path C:\Users\Admin\AppData\Local\Temp\{3100735F-DB14-4545-AAC0-0ED69EA251E0}
- Size 4KB
- SHA256 13601c57a8d5d91f16950f6fbb3c586062bc253eda56520538951d9d233ec2ed
- MD5 225830d9208b9c3620dd610586a4a300
- SHA1 2a9f1d082686390725a6c05c5e9285d221516e60
- SHA512 a6fbe1b77cd6541b24b8c45b27da6c1ce0727def7ac30cfce660efd9a9d0d3c726392700e242269e1aa5afe00a33d78a5dfe935ab8290fad5c7e7c6c2e776a77
- SSDEEP 6:RaZfjYyfB3h1RRXUnf3T/8+pzvHFKmimaQm/Rujlw//0lweI/gZQmNRujd:RaNjYyf9/UfD/vLdi6vWf/rT
- MD5 SHA1 SHA512 SSDEEP
- Path C:\Users\HLJkNskOq.README.txt
- Size 10KB
- SHA256 56a47073899979f24a9c325543d53c9362c35a960f6998d51860033413272855
- MD5 341e5f666ea6f706e952de833c7c57f3
- SHA1 d987b72e0a45e500fc89adb5f86c39b393c6555f
- SHA512 5ddfc68f514e42671f1de0e7e569f822d086dba818d5adfe56dbe15f66307a3078d2d7176640b419eb4ae2da963e3bef4671b4c3cfae6a839aafeedc557efeaa
- SSDEEP 192:vWVVo2yaRv7D+0v0nkwtn30hj2oJuQJfEpunqEzT/yF0X4FxlZcUFdsSJpVutJvA:OVV9IN0j/AzrxZcUFdsSJpVutJpLrFNW
- MD5 SHA1 SHA512 SSDEEP
- Path F:\$RECYCLE.BIN\S-1-5-21-3808065738-1666277613-1125846146-1000\DDDDDDDDDDD
- Size 129B
- SHA256 14ea567c42ebac4498718c0551415d81b4affdf3f70c64227fba72222a558f0c
- MD5 e4aa05d099dc7a2bcabe7f4e5c390d3e
- SHA1 4aaed2c12586bc0d48159bfcf5d9607799fa78a2
- SHA512 85499a9f0e4c8ed2adaaa629f51a573293d94adf1ab36993f108091226eaa42fcb21c16b53b8e231709ff00f4cec68f18310cd8a54586d2c6d19d88d66e9f092
- MD5 SHA1 SHA512