General
-
Target
xnfipyy.inf
-
Size
38KB
-
Sample
211109-g3m56sbfhm
-
MD5
18ff6706dac4cda1c85afa02495f4149
-
SHA1
a9b70524165713bcb147ca22c95475c091232904
-
SHA256
4889479cc52b989f745d78a483c62fabaa70e7f078a82a5656c8a454e599bac5
-
SHA512
d3c2ae6497eeaa323544e72a39d3dfe95a5701054944cf09307cfc2b6e70011ea93035e1523739af3a8b39022b7fe3ca7ebc95493731b4184132f2ae783582d9
Static task
static1
Behavioral task
behavioral1
Sample
xnfipyy.inf.dll
Resource
win7-en-20211014
Behavioral task
behavioral2
Sample
xnfipyy.inf.dll
Resource
win10-en-20211104
Malware Config
Extracted
C:\Users\Admin\Desktop\readme.txt
magniber
http://2c683a18a83022505adujyxylz.w3disbrllt7cfknxuutwevchixw5vbyc4ujvg5cz3u57nryezwqgwnad.onion/dujyxylz
http://2c683a18a83022505adujyxylz.wonsre.space/dujyxylz
http://2c683a18a83022505adujyxylz.wheelgo.sbs/dujyxylz
http://2c683a18a83022505adujyxylz.fitsbus.uno/dujyxylz
http://2c683a18a83022505adujyxylz.amlack.quest/dujyxylz
Extracted
C:\Users\Admin\Desktop\readme.txt
magniber
http://62c4684026f46e107cdujyxylz.w3disbrllt7cfknxuutwevchixw5vbyc4ujvg5cz3u57nryezwqgwnad.onion/dujyxylz
http://62c4684026f46e107cdujyxylz.wonsre.space/dujyxylz
http://62c4684026f46e107cdujyxylz.wheelgo.sbs/dujyxylz
http://62c4684026f46e107cdujyxylz.fitsbus.uno/dujyxylz
http://62c4684026f46e107cdujyxylz.amlack.quest/dujyxylz
Targets
-
-
Target
xnfipyy.inf
-
Size
38KB
-
MD5
18ff6706dac4cda1c85afa02495f4149
-
SHA1
a9b70524165713bcb147ca22c95475c091232904
-
SHA256
4889479cc52b989f745d78a483c62fabaa70e7f078a82a5656c8a454e599bac5
-
SHA512
d3c2ae6497eeaa323544e72a39d3dfe95a5701054944cf09307cfc2b6e70011ea93035e1523739af3a8b39022b7fe3ca7ebc95493731b4184132f2ae783582d9
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
-