Analysis

  • max time kernel
    48s
  • max time network
    34s
  • platform
    windows10-ltsc 2021_x64
  • resource
    win10ltsc2021-20241211-en
  • resource tags

    arch:x64arch:x86image:win10ltsc2021-20241211-enlocale:en-usos:windows10-ltsc 2021-x64system
  • submitted
    10-01-2025 12:56

General

  • Target

    21a7fba68d5abd4c3837521c2e86a03454e98a4f9517fa83ff00c47fb3c4cd44.ps1

  • Size

    1.1MB

  • MD5

    21d9746b4d1970e0e38ce62e2f36270e

  • SHA1

    126d0de73b2c8e9276806a02e5c2ee3d1f1a7e7d

  • SHA256

    21a7fba68d5abd4c3837521c2e86a03454e98a4f9517fa83ff00c47fb3c4cd44

  • SHA512

    4045eca5e5f4f97f530837692256554e3687aafbebd58b53f7bd6f02de3d0c4a3c8c7efbd3edc45971076b435192937f227f6a7a6e67916ff628397bef4b4992

  • SSDEEP

    24576:XIJElvW93GPtN3jQeiKAsaLQG0Q0uidX/V:4Q15

Malware Config

Extracted

Path

F:\teViazD4k.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://lockbitsupa7e3b4pkn4mgkgojrl5iqgx24clbzc4xm7i6jeetsia3qd.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: 0FADF2D6517D3F4BA56234BCC7899953 <<<<< >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> 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.

  • Lockbit family
  • Renames multiple (159) files with added filename extension

    This suggests ransomware activity of encrypting all the files on the system.

  • Deletes itself 1 IoCs
  • Executes dropped EXE 1 IoCs
  • Sets desktop wallpaper using registry 2 TTPs 2 IoCs
  • Suspicious use of NtSetInformationThreadHideFromDebugger 12 IoCs
  • Command and Scripting Interpreter: PowerShell 1 TTPs 1 IoCs

    Using powershell.exe command.

  • System Location Discovery: System Language Discovery 1 TTPs 2 IoCs

    Attempt gather information about the system language of a victim in order to infer the geographical location of that host.

  • Checks SCSI registry key(s) 3 TTPs 3 IoCs

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

  • Modifies registry class 5 IoCs
  • Opens file in notepad (likely ransom note) 1 IoCs
  • Suspicious behavior: EnumeratesProcesses 31 IoCs
  • Suspicious behavior: RenamesItself 26 IoCs
  • Suspicious use of AdjustPrivilegeToken 64 IoCs
  • Suspicious use of FindShellTrayWindow 42 IoCs
  • Suspicious use of SendNotifyMessage 41 IoCs
  • Suspicious use of WriteProcessMemory 7 IoCs

Processes

  • C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    powershell.exe -ExecutionPolicy bypass -File C:\Users\Admin\AppData\Local\Temp\21a7fba68d5abd4c3837521c2e86a03454e98a4f9517fa83ff00c47fb3c4cd44.ps1
    1⤵
    • Command and Scripting Interpreter: PowerShell
    • Suspicious behavior: EnumeratesProcesses
    • Suspicious use of AdjustPrivilegeToken
    • Suspicious use of WriteProcessMemory
    PID:3984
    • C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
      "C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe" -ex bypass -nonI C:\Users\Admin\AppData\Local\Temp\21a7fba68d5abd4c3837521c2e86a03454e98a4f9517fa83ff00c47fb3c4cd44.ps1
      2⤵
      • Sets desktop wallpaper using registry
      • Suspicious use of NtSetInformationThreadHideFromDebugger
      • System Location Discovery: System Language Discovery
      • Modifies registry class
      • Suspicious behavior: EnumeratesProcesses
      • Suspicious use of AdjustPrivilegeToken
      • Suspicious use of WriteProcessMemory
      PID:2320
      • C:\ProgramData\CF17.tmp
        "C:\ProgramData\CF17.tmp"
        3⤵
        • Deletes itself
        • Executes dropped EXE
        • Suspicious use of NtSetInformationThreadHideFromDebugger
        • System Location Discovery: System Language Discovery
        • Suspicious behavior: RenamesItself
        PID:3220
  • C:\Windows\system32\taskmgr.exe
    "C:\Windows\system32\taskmgr.exe" /0
    1⤵
    • Checks SCSI registry key(s)
    • Suspicious behavior: EnumeratesProcesses
    • Suspicious use of AdjustPrivilegeToken
    • Suspicious use of FindShellTrayWindow
    • Suspicious use of SendNotifyMessage
    PID:4788
  • C:\Windows\system32\NOTEPAD.EXE
    "C:\Windows\system32\NOTEPAD.EXE" C:\Users\Admin\Desktop\teViazD4k.README.txt
    1⤵
    • Opens file in notepad (likely ransom note)
    PID:2884

Network

MITRE ATT&CK Enterprise v15

Replay Monitor

Loading Replay Monitor...

Downloads

  • C:\ProgramData\CF17.tmp

    Filesize

    14KB

    MD5

    294e9f64cb1642dd89229fff0592856b

    SHA1

    97b148c27f3da29ba7b18d6aee8a0db9102f47c9

    SHA256

    917e115cc403e29b4388e0d175cbfac3e7e40ca1742299fbdb353847db2de7c2

    SHA512

    b87d531890bf1577b9b4af41dddb2cdbbfa164cf197bd5987df3a3075983645a3acba443e289b7bfd338422978a104f55298fbfe346872de0895bde44adc89cf

  • C:\Users\Admin\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive

    Filesize

    1KB

    MD5

    a0659b18568c8dc473730b20a024930e

    SHA1

    e9aa76b230082e84b1147ce8246b7e8bdfe4ccc4

    SHA256

    bb0d87d5206aa2488b5ae56a9f20faa26bbe05dfa938e53996bf3d57725df57e

    SHA512

    cc6ae820f9695a40f3e85044c97203369be1c991bcd5b9a81cf28ee2d5050add4a3d28be1543ed13b4a9d44b90c55fd1897082c3bb147b08d02cd93cbbde7bb8

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

    Filesize

    1.1MB

    MD5

    9aa619dfd2d6ea86c1abf40142d857a5

    SHA1

    8c7af378771f1ce1c84f97176d3574ef040c095a

    SHA256

    525f81032eae26ea8e2cdb782730e1e61c7a8a48d9f0c431517cb4d0ed7f3c5b

    SHA512

    e6d290d7b9fd5709c7834a0dc98c5ca89b67ad501044112936f62fd3450e2500a5c86bc7fb143c2ecaf408f56db227bcd0b831c5aed3446e7a753a73133dcf2f

  • C:\Users\Admin\AppData\Local\Temp\__PSScriptPolicyTest_vdkvhasa.gqs.ps1

    Filesize

    60B

    MD5

    d17fe0a3f47be24a6453e9ef58c94641

    SHA1

    6ab83620379fc69f80c0242105ddffd7d98d5d9d

    SHA256

    96ad1146eb96877eab5942ae0736b82d8b5e2039a80d3d6932665c1a4c87dcf7

    SHA512

    5b592e58f26c264604f98f6aa12860758ce606d1c63220736cf0c779e4e18e3cec8706930a16c38b20161754d1017d1657d35258e58ca22b18f5b232880dec82

  • F:\teViazD4k.README.txt

    Filesize

    10KB

    MD5

    fcf644ab0759c2eb213854f48b8ae265

    SHA1

    6fd684c81de2d9e83c0762bb591b17db306734d6

    SHA256

    9fde77e2098c5e5105e18bd18e021ef04f1cf1a48e2ebf8c45fe317ade799077

    SHA512

    fd89ad1984041f68066f7cc58ad748cf8294c361f8945a7a1ebe7afab1168e331bda08b2f94aff1faba36c5c43de9b7a64750a7ea7dd09123823e72dbd8ef982

  • memory/2320-58-0x000000000C420000-0x000000000C431000-memory.dmp

    Filesize

    68KB

  • memory/2320-21-0x0000000075140000-0x00000000758F1000-memory.dmp

    Filesize

    7.7MB

  • memory/2320-17-0x000000007514E000-0x000000007514F000-memory.dmp

    Filesize

    4KB

  • memory/2320-18-0x0000000002410000-0x0000000002446000-memory.dmp

    Filesize

    216KB

  • memory/2320-19-0x0000000005000000-0x00000000056CA000-memory.dmp

    Filesize

    6.8MB

  • memory/2320-20-0x0000000075140000-0x00000000758F1000-memory.dmp

    Filesize

    7.7MB

  • memory/2320-62-0x000000000C4B0000-0x000000000C4B8000-memory.dmp

    Filesize

    32KB

  • memory/2320-22-0x0000000004D80000-0x0000000004DA2000-memory.dmp

    Filesize

    136KB

  • memory/2320-23-0x0000000004E20000-0x0000000004E86000-memory.dmp

    Filesize

    408KB

  • memory/2320-24-0x0000000004E90000-0x0000000004EF6000-memory.dmp

    Filesize

    408KB

  • memory/2320-25-0x00000000056D0000-0x0000000005A27000-memory.dmp

    Filesize

    3.3MB

  • memory/2320-326-0x0000000075140000-0x00000000758F1000-memory.dmp

    Filesize

    7.7MB

  • memory/2320-36-0x0000000005DC0000-0x0000000005DDE000-memory.dmp

    Filesize

    120KB

  • memory/2320-37-0x0000000005E00000-0x0000000005E4C000-memory.dmp

    Filesize

    304KB

  • memory/2320-38-0x000000000C7C0000-0x000000000CE3A000-memory.dmp

    Filesize

    6.5MB

  • memory/2320-39-0x000000000BFA0000-0x000000000BFBA000-memory.dmp

    Filesize

    104KB

  • memory/2320-43-0x0000000075140000-0x00000000758F1000-memory.dmp

    Filesize

    7.7MB

  • memory/2320-42-0x0000000071CE0000-0x0000000072037000-memory.dmp

    Filesize

    3.3MB

  • memory/2320-53-0x000000000C100000-0x000000000C11E000-memory.dmp

    Filesize

    120KB

  • memory/2320-325-0x000000000C630000-0x000000000C652000-memory.dmp

    Filesize

    136KB

  • memory/2320-41-0x0000000071320000-0x000000007136C000-memory.dmp

    Filesize

    304KB

  • memory/2320-40-0x000000000C1C0000-0x000000000C1F2000-memory.dmp

    Filesize

    200KB

  • memory/2320-55-0x000000000C200000-0x000000000C2A3000-memory.dmp

    Filesize

    652KB

  • memory/2320-56-0x000000000C2C0000-0x000000000C2CA000-memory.dmp

    Filesize

    40KB

  • memory/2320-57-0x000000000C4F0000-0x000000000C586000-memory.dmp

    Filesize

    600KB

  • memory/2320-317-0x0000000075140000-0x00000000758F1000-memory.dmp

    Filesize

    7.7MB

  • memory/2320-59-0x000000000C470000-0x000000000C47E000-memory.dmp

    Filesize

    56KB

  • memory/2320-60-0x000000000C480000-0x000000000C494000-memory.dmp

    Filesize

    80KB

  • memory/2320-61-0x000000000C4C0000-0x000000000C4DA000-memory.dmp

    Filesize

    104KB

  • memory/2320-316-0x0000000075140000-0x00000000758F1000-memory.dmp

    Filesize

    7.7MB

  • memory/2320-54-0x0000000075140000-0x00000000758F1000-memory.dmp

    Filesize

    7.7MB

  • memory/2320-314-0x000000000C630000-0x000000000C652000-memory.dmp

    Filesize

    136KB

  • memory/2320-309-0x000000000C630000-0x000000000C652000-memory.dmp

    Filesize

    136KB

  • memory/2320-112-0x000000000C630000-0x000000000C652000-memory.dmp

    Filesize

    136KB

  • memory/2320-298-0x000000000C630000-0x000000000C652000-memory.dmp

    Filesize

    136KB

  • memory/2320-92-0x000000000C630000-0x000000000C652000-memory.dmp

    Filesize

    136KB

  • memory/2320-97-0x000000000C630000-0x000000000C652000-memory.dmp

    Filesize

    136KB

  • memory/2320-85-0x000000000C630000-0x000000000C652000-memory.dmp

    Filesize

    136KB

  • memory/2320-78-0x000000000C630000-0x000000000C652000-memory.dmp

    Filesize

    136KB

  • memory/2320-76-0x000000007514E000-0x000000007514F000-memory.dmp

    Filesize

    4KB

  • memory/2320-77-0x0000000075140000-0x00000000758F1000-memory.dmp

    Filesize

    7.7MB

  • memory/3984-16-0x00007FFCA5420000-0x00007FFCA5EE2000-memory.dmp

    Filesize

    10.8MB

  • memory/3984-1-0x000001C67DA40000-0x000001C67DA62000-memory.dmp

    Filesize

    136KB

  • memory/3984-13-0x00007FFCA5420000-0x00007FFCA5EE2000-memory.dmp

    Filesize

    10.8MB

  • memory/3984-11-0x00007FFCA5420000-0x00007FFCA5EE2000-memory.dmp

    Filesize

    10.8MB

  • memory/3984-0-0x00007FFCA5423000-0x00007FFCA5425000-memory.dmp

    Filesize

    8KB

  • memory/3984-12-0x00007FFCA5420000-0x00007FFCA5EE2000-memory.dmp

    Filesize

    10.8MB

  • memory/4788-71-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB

  • memory/4788-69-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB

  • memory/4788-75-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB

  • memory/4788-72-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB

  • memory/4788-64-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB

  • memory/4788-70-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB

  • memory/4788-63-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB

  • memory/4788-65-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB

  • memory/4788-73-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB

  • memory/4788-74-0x000001686FA80000-0x000001686FA81000-memory.dmp

    Filesize

    4KB