General
-
Target
1.dll
-
Size
38KB
-
Sample
210829-tsgxrany9s
-
MD5
f6202e6f4b35f20f7c186d0440a85db9
-
SHA1
fe9211e7e811e1826dd401a2a7f1ac92ac8613ad
-
SHA256
f66e9e0a8847f5c0d3a11e1f61fe70f236688474760038e2bc1fbcc637b08fd1
-
SHA512
85a43634be204d888d319b398b742b086cffe0db391588bb304851644c8ef15c27434e794b821e0ed002b540dc41dc83333942867632ce271baa1182a24d3583
Static task
static1
Behavioral task
behavioral1
Sample
1.dll
Resource
win7v20210408
Behavioral task
behavioral2
Sample
1.dll
Resource
win10v20210408
Malware Config
Extracted
C:\Users\Admin\Desktop\readme.txt
magniber
http://d2cc88480e784a7002svbdthwdw.ntjflrx6uhwcmfhnn3yewv2wfhtqtjyfkvyrvjz4wuo6uw33yw7sfiid.onion/svbdthwdw
http://d2cc88480e784a7002svbdthwdw.upquote.xyz/svbdthwdw
http://d2cc88480e784a7002svbdthwdw.armythe.club/svbdthwdw
http://d2cc88480e784a7002svbdthwdw.aredata.site/svbdthwdw
http://d2cc88480e784a7002svbdthwdw.whorest.top/svbdthwdw
Extracted
C:\Users\Admin\Desktop\readme.txt
magniber
http://78146e4834b06a607svbdthwdw.ntjflrx6uhwcmfhnn3yewv2wfhtqtjyfkvyrvjz4wuo6uw33yw7sfiid.onion/svbdthwdw
http://78146e4834b06a607svbdthwdw.upquote.xyz/svbdthwdw
http://78146e4834b06a607svbdthwdw.armythe.club/svbdthwdw
http://78146e4834b06a607svbdthwdw.aredata.site/svbdthwdw
http://78146e4834b06a607svbdthwdw.whorest.top/svbdthwdw
Targets
-
-
Target
1.dll
-
Size
38KB
-
MD5
f6202e6f4b35f20f7c186d0440a85db9
-
SHA1
fe9211e7e811e1826dd401a2a7f1ac92ac8613ad
-
SHA256
f66e9e0a8847f5c0d3a11e1f61fe70f236688474760038e2bc1fbcc637b08fd1
-
SHA512
85a43634be204d888d319b398b742b086cffe0db391588bb304851644c8ef15c27434e794b821e0ed002b540dc41dc83333942867632ce271baa1182a24d3583
Score10/10-
Magniber Ransomware
Ransomware family widely seen in Asia being distributed by the Magnitude exploit kit.
-
Process spawned unexpected child process
This typically indicates the parent process was compromised via an exploit or macro.
-
Modifies extensions of user files
Ransomware generally changes the extension on encrypted files.
-
Checks computer location settings
Looks up country code configured in the registry, likely geofence.
-
Suspicious use of SetThreadContext
-