General
- Target 2026-06-27_d1f86a7b3cccc39bc6b00ae40961cdaf_wannacry
- Size 241KB
- Sample260629-c4cnlsbv4s
- SHA256 624559f20e7151bca4f19058b8cd9b38c9fd904ae62a9f535da759f4cff52993
- MD5 d1f86a7b3cccc39bc6b00ae40961cdaf
- SHA1 8f783779b09f1373508fdec2a0609fdb952edfe7
- SHA512 9e3d88656c5ee2207c3dc7132b710ac4056b29a0b98d6d403273317c0ab77401de6fb8ec5c059ec7bd1f92ed77be8033965c2fa2cc83f80db1f46aa31ac0b5e8
- SSDEEP 3072:lz30T76S7GJ3oaFSdE/bQPIEyC13wdVtYjmFRWccTjJyOC6Ymapz9OUSMp+00HwX:p30T76fbodKFRWhVyOC6qsUSMQHwTM5
- TLSH T106342B1BB3A30EF8C657C17942E6D771AA31F8250321F91F0758DB332E22D545FAAA58
- MD5 SHA1 SHA512 SSDEEP TLSH
Score
10/10
Static task
static1
2 signatures
Behavioral task
behavioral1
Sample
2026-06-27_d1f86a7b3cccc39bc6b00ae40961cdaf_wannacry.exe
Resource
win10v2004-20260513-en
3 signatures
150 seconds
Behavioral task
behavioral2
Sample
2026-06-27_d1f86a7b3cccc39bc6b00ae40961cdaf_wannacry.exe
Resource
win11ltsc2024-20260617-en
17 signatures
150 seconds
Malware Config
Targets
-
- Target 2026-06-27_d1f86a7b3cccc39bc6b00ae40961cdaf_wannacry
- Size 241KB
- SHA256 624559f20e7151bca4f19058b8cd9b38c9fd904ae62a9f535da759f4cff52993
- MD5 d1f86a7b3cccc39bc6b00ae40961cdaf
- SHA1 8f783779b09f1373508fdec2a0609fdb952edfe7
- SHA512 9e3d88656c5ee2207c3dc7132b710ac4056b29a0b98d6d403273317c0ab77401de6fb8ec5c059ec7bd1f92ed77be8033965c2fa2cc83f80db1f46aa31ac0b5e8
- SSDEEP 3072:lz30T76S7GJ3oaFSdE/bQPIEyC13wdVtYjmFRWccTjJyOC6Ymapz9OUSMp+00HwX:p30T76fbodKFRWhVyOC6qsUSMQHwTM5
- TLSH T106342B1BB3A30EF8C657C17942E6D771AA31F8250321F91F0758DB332E22D545FAAA58
- MD5 SHA1 SHA512 SSDEEP TLSH
Score9/10-
Detects command variations typically used by ransomware
-
Boot or Logon Autostart Execution: Active Setup
Adversaries may achieve persistence by adding a Registry key to the Active Setup of the local machine.
-
Enumerates connected drives
Attempts to read the root path of hard drives other than the default C: drive.
-
Maps connected drives based on registry
Disk information is often read in order to detect sandboxing environments.
-
Suspicious use of NtSetInformationThreadHideFromDebugger