General
-
Target
tempa.dll
-
Size
38KB
-
Sample
210827-nkk9ea3yax
-
MD5
b90ea37466ff51b92394c61642360f27
-
SHA1
1137d8f12c1f1c1a4cb16b5f36a6e297b53d969c
-
SHA256
d7ac1232f9860102bc977ecf949543f83f3d651d7a1e55af3c1d0bacddf68a2f
-
SHA512
ade05a09a533c08be307303abe5fcff2fe62b23b73da1b1e1b0d9c83c8d4a93a250fc4500264f2dc7357a4c51633ed7548ec23c57a689f2045086f7de3874220
Static task
static1
Behavioral task
behavioral1
Sample
tempa.dll
Resource
win7v20210410
Behavioral task
behavioral2
Sample
tempa.dll
Resource
win10v20210408
Malware Config
Extracted
C:\Users\Admin\Desktop\readme.txt
magniber
http://2260b4d0f014c040d2hvbluctpp.7cdpfkmp6tm2t7ce6m7fdldv4eor5jxotxj6v23djv73mwfstpq3ebad.onion/hvbluctpp
http://2260b4d0f014c040d2hvbluctpp.burybig.xyz/hvbluctpp
http://2260b4d0f014c040d2hvbluctpp.centone.top/hvbluctpp
http://2260b4d0f014c040d2hvbluctpp.joyfits.site/hvbluctpp
http://2260b4d0f014c040d2hvbluctpp.dumpour.space/hvbluctpp
Extracted
C:\Users\Admin\Desktop\readme.txt
magniber
http://f0607a18faec44d0c2hvbluctpp.7cdpfkmp6tm2t7ce6m7fdldv4eor5jxotxj6v23djv73mwfstpq3ebad.onion/hvbluctpp
http://f0607a18faec44d0c2hvbluctpp.burybig.xyz/hvbluctpp
http://f0607a18faec44d0c2hvbluctpp.centone.top/hvbluctpp
http://f0607a18faec44d0c2hvbluctpp.joyfits.site/hvbluctpp
http://f0607a18faec44d0c2hvbluctpp.dumpour.space/hvbluctpp
Targets
-
-
Target
tempa.dll
-
Size
38KB
-
MD5
b90ea37466ff51b92394c61642360f27
-
SHA1
1137d8f12c1f1c1a4cb16b5f36a6e297b53d969c
-
SHA256
d7ac1232f9860102bc977ecf949543f83f3d651d7a1e55af3c1d0bacddf68a2f
-
SHA512
ade05a09a533c08be307303abe5fcff2fe62b23b73da1b1e1b0d9c83c8d4a93a250fc4500264f2dc7357a4c51633ed7548ec23c57a689f2045086f7de3874220
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
-