r/LinuxMalware • u/mmd0xFF • Apr 19 '20
r/LinuxMalware • u/mmd0xFF • Mar 30 '19
New China ELF malware DDoS'er "Linux/DDoSMan", bot and C2 toolkit
r/LinuxMalware • u/mmd0xFF • Feb 11 '20
New "SystemTen" botnet miner threat, now w/other "supper savvy" LOL-packed ELF and.. "atomic" bash-base64 parsers :)
The threat is still there, thx RJ+Ceph for the fun poke of ELF bins. My unpacking, analysis for that bins is in here (The IOC raw info is all in there too). Be aware of low detection ratio.
Basically they still try on poorly (exec with deletion afterwards, no injection) effort to be fileless, more "insane efforts" in ELF packer, and execution series of "bash" parsed encoded base64 commands executed by "sh".. as its bot installer, bot updater, miner installer and updater, with the flavor of onions, using latest XMrig w/hardcoded pools .. shortly, it's a come-back.
Hint: Someone in PRC/China is persistently "sponsoring a serious big effort" in mass crypto-mining here.
MalwareMustDie!
r/LinuxMalware • u/mmd0xFF • Feb 15 '23
Explanation about this subreddit (README)
This post is to elaborate the contents of this subreddit, for the new design that has not had sidebar menu. The subreddit posts of Linux / ELF malware is for RE purpose, it may help you on learning to analyze a Linux malware. This subreddit is single-modded and the site's contents are MalwareMustDie.org's @unixfreaxjp Linux threat research material. You may link to any of the contents or this subreddit with mention to the original researcher (unixfreaxjp).
You switch the view mode: RSS | Mobile | NewReddit | OldReddit
You may want to discuss about my analysis but I am not good in chatting, if you have question please upload your text from here.
So about the contents:
These are the latest Linux Malware cases I have reversed and posted:
And these are my older Linux malware analysis, I called it "analysis museum":
Linux/Bashdoor(Gafgyt/Torlus/Qbot (first router campaign case actor: LizardSquad)
Linux/Bashdoor(Gafgyt/Torlus/Qbot 1st found in shellshock, actor: LizardSquad)
..and lastly, you may also want to visit other similar sub-reddits too like:
Cheers! - unixfreaxjp -
r/LinuxMalware • u/mmd0xFF • 8d ago
MMD-0070-2026 - Linux/Hajime (focus at hexstring-pushed a tiny ARM ELF fileless downloader)
blog.malwaremustdie.orgr/LinuxMalware • u/mmd0xFF • 8d ago
MMD-071-2026 Linux/KinsingBot a "bad-bad" designed botnet
blog.malwaremustdie.orgr/LinuxMalware • u/mmd0xFF • Oct 28 '19
My HACKLU2019 Keynote: Linux fileless malware infection, process injection and post-exploitation framework
I have done my keynote presentation in HackLU 2019 regarding to the subject. The slide is 148pages long and it was (had to be) done within 45minutes. The conference folks can read the slides & watch the video slowly afterwards.
It was a nice LONG (45m) techie talk, the point of the presentation is for the better security and defense purpose in relation to mitigate the post-exploitation attack using process injection that leave all of us mostly with the fileless state. So, it is explaining how indeed the breakdown of a post-exploitation attacks on Linux, how the process injection can be happened in user space, in kernel or in ramdisk, and how the fileless state can be implemented, those are explaination needed in order for us to killchain these attacks in the future to prevent them better.
During the presentation I was like trying to mix between ideology in security, technical concept and actual incident cases with several examples that can make IR more practical and interactively involved in the talk, with putting several reverse engineering codes for the RE engineers that may see the talk to follow the flow in dissecting those cases.
As the follow up from the talk, there are some reading takeaways, and Q & A I have listed in MalwareMustDie blog. Hope you can find them useful to make a better understanding of the slides and the video.
We don't share the material directly from any ranks of MMD openly, HackLU has them. TLP AMBER is applied in our team for the sharing purpose, and we have the good explanation of it, written in our blog. But if you are in the security field or in Linux development, and you don't reach the materials yet, feel free to PM me by explaining about yourself and why you need to see them. We don't share it to unknown security people.
I am planning to make the defense workshop or hackathon for this kind of threat on Linux in the FIRST conference next year, if you are in IR maybe you could come and join the venet so we can discuss and demo many approach for this matter. I will let you know.
Thank you very much for the reading and always support.
r/LinuxMalware • u/mmd0xFF • Mar 25 '19
Fixing Mirai version Miori crypted configuration
r/LinuxMalware • u/mmd0xFF • Jan 04 '19
Linux/HelloBot (new bot/backdoor w/china origin ELF malware)
r/LinuxMalware • u/mmd0xFF • Jun 01 '18
Reversing a linux process injector "mandibule" w/r2
r/LinuxMalware • u/mmd0xFF • Jan 27 '19
Now is year 2019 and we still see ELF Tsunami/Kaiten and Perl DDoS threat. These malware are almost 20 years old!
r/LinuxMalware • u/mmd0xFF • Jan 15 '20
MMD-0065-2020 - Linux/Mirai-Fbot's new encryption explained (RE of ARM v5 binary, post-forensics)
r/LinuxMalware • u/mmd0xFF • Apr 20 '19
Fun in dissecting "LSD Packer" ELF GoLang Miner installer/loader made by "Hippies" China SystemTen (aka Rocke) Gang
r/LinuxMalware • u/mmd0xFF • Jan 20 '18
"Vulcan" aka Linux/"Rebirth" or "Katrina" (variant of qbot/torlus basis). another Ddos malware weaponized w/: router exploitation, plenty of IoT scanners & mirai stuff, aimed routers, modems or servers.
r/LinuxMalware • u/mmd0xFF • May 29 '20
Linux/Rebirth or Vulcan in 2020 (Gaygyt evolved)
r/LinuxMalware • u/mmd0xFF • May 23 '20
[Announcement] My own kernelmode[.]info Linux/Malware reports is merged in here
As some of you maybe know that I involved in contribution for Linux/Malware at the kernelmode.info forum, before I left it.
I would like to announce that the 16 threads of Linux/Malware analysis, either those were ones I first initiated it, or at those threads were having my analysis and writing efforts, are all backup up and merged in this repository successfully. The backup is only taking the first page of each thread due to the size limitation in the storage, however it is important to proof the first malware that has been firstly found or firstly named during MMD effort and those has been decided on my analysis desk.
What I wrote in the kernelmode forum are important because at the time I thought I was being between friendlies, therefore under the strong trust level many of the Linux/Malware threat analysis insights were shared over there.
The data has been successfully saved as offline web-pages, and for this repository purpose only the first page is shared, by the link to a GitHub storage account as the Open Source(feel free to analyze them).
Noted ("THIS IS IMPORTANT!): as long as you don't click the URL/links in those saved pages and just read them and "go back" here after reading, you will only browse the first page under the GitHub's service/host environment < again, please note this. If you want to read further and click some links on that first page, you will be redirected to the "Archive of KernelMode" server located at the below ISP and network details. I have nothing to do with the service and I don't know who is managing it, you can access it with your own risk. (Risk like, i.e. your access can be recorded by unknown parties, etc, I don't know..):
IP: 81.95.1.72
FQDN hostname: mif.h5l.org.
ASN: AS201011
ISP: OxygemDigital Inc, Victoria
Country: SeychellesTo recognize those migrated threads you can grep the characters "^KM" in the right-side menu list of Linux malware, and if you did it well, these are the list that has been added:
(65) : - Linux/Pscan and SSHscan ^KM
(71) : - Linux/KillFile ^KM
(75) : - Linux/BangSyn ^KM
(85) : - Linux/DTool ^KM
(95) : - Linux/Bashdoor(Gafgyt/Torlus/Qbot 1st found ^KM
(101): - Linux/Encoder ^KM
(107): - Linux/Torte ^KM
(123): - Linux/XorDDOS first found/rpt ^KM
(143): - Linux/ChinaZ "the beginning" 1st found ^KM
(145): - Linux/GoARMBot ^KM
(149): - Linux/AESDDoS ^KM
(153): - Linux/.Iptables or Iptablex ^KM
(159): - Linux/Mayhem ^KM
(161): - Linux/BossaBot ^KM
(167): - Linux/Elknot ^KM
(179): - Linux/Kaiten (Tsunami) ^KM
Lastly, I would like to thank kernelmode moderator @Xylit0l, who kindly allowed the backing up process to run smoothly, and to acknowledge the merge of the backups into this repository.
So please help yourself to read those analysis. There are a lot of them has not been covered by other places due to my limitation time to write to MMD blogs or other reporting forms.
I really hope that /r/LinuxMalware subreddit can be used for the future and stable media for the posting of Linux malware research, as a rich repository, for the future, and learning from the past, all of the data posted in here are backed up before posted.
In the future, after the mechanism of subreddit is mastered, I will share the posting access to others. There are many more analysis data that need to build first, I will need at least another year to cleaning up the backlog reports I made in the past.
Thank you and best regards
mmd0xFF
r/LinuxMalware • u/mmd0xFF • May 21 '20
Linux/KAITEN AK47 w/Telnet Scanner & EchoLoaders (hexstrings) injection attacks on IoT
r/LinuxMalware • u/mmd0xFF • Mar 14 '20
The "echo" loader vs "telnet" loader in ELF malware Mirai FBOT (ARM EABI reversing)
r/LinuxMalware • u/mmd0xFF • Mar 08 '20
Some issues w/ recent Hajime IoT linux malware & its botnet
I made a thread in twitter for this issue, hopefully this will improve the situation.
r/LinuxMalware • u/mmd0xFF • Mar 09 '20
Checking on Linux/Mozi, trying to make a comeback (thread w/links to IOC)
r/LinuxMalware • u/mmd0xFF • Jan 14 '18
First ARC (risc-base) Core targeted ELF malware, was just found
The malware is Mirai, Okiru variant. VT: https://www.virustotal.com/en/file/2356c1d64995ee825c728957f7428543101c3271ac46e78ce2c98278a4480e4d/analysis/
First spotted malware sample in the computer industry to aim ARC cpu ITW.
Found by: @unixfreaxjp of MalwareMustDie team, on January 14, 2018
r/LinuxMalware • u/mmd0xFF • Jan 14 '18
Linux/SS aka Shark - hacktool SYN scanner w/PCAP interface
Analysis is in the VT comment: https://www.virustotal.com/en/file/97093a1ef729cb954b2a63d7ccc304b18d0243e2a77d87bbbb94741a0290d762/analysis/ Use the old VirusTotal webGUI to read it in better looks.
r/LinuxMalware • u/mmd0xFF • Jan 08 '18
Quick notes for Okiru & Satori variant of Mirai
From what we observe so far. these two types of Linux IoT DDoS'er malware are very different, (among several of similar characteristic), from the way they are coded. their plan to pick the targets, to how they are actually herded (or managed). So we think it is better for security filtration platforms to have different signatures to trace & detect each of these variants (to be manageable to next variants to come too), for that I am sharing our YARA signature I coded for detection of Okiru and Satori
Some simple highlights to differ Okiru to Satori variant:
The config is different, Okiru variant's config is encrypted in two parts w/ telnet bombardment password encrypted, Satori does not split it in 2parts and doesn't encrypt brute default passwords. Also Okiru's telnet attack login information is a bit longer (can be up to 114 credentials, max counted), while Satori is having different and shorter database.
Satori seems to have "TSource Engine Query" common Distributed "Reflective" (DRDoS) attack function via random UDP, while Okiru does not seem to have this function,
The infection follow up commands written in both Okiru and Satori in their configurations are a bit different, showing possibility that they don't seem sharing a same "herding environment",
(up to) Four types of router attack CVE-2017-17215 exploit code has only being spotted hard coded in Okiru variant, yet Satori does not use these exploits at all,
Satori (see VirusTotal for sample+textual code in VT's comment part for reversed code) is using small embedded ELF trojan downloaders to download other architecture binaries which were coded differently compared to Okiru ones (see sample+textual reversed code is in VT comment),
additional: Okiru is (recently) having the ARC processor's compiled version, and Satori is not (at the time this report is written).
(there are more minors stuff too that you can notice using the pictures shown in previous points, like differences in usage of watchdog checking, the usage of command "echo -en \x..." etc etc)
Hashes:
Okiru:
9c677dd17279a43325556ec5662feba0
214d8e84823bfba7adfe302aa6786d5a
c892092f58761b29dbd965b977412c10
17bdf1e6692bba7ee19fc837a457d122
24fc15a4672680d92af7edb2c3b2e957
5fb5d4a3f43a1202a973fc8328aede57
808eaf4b336880a5d38a1d690fbd46b6
4215c48693e00cc683ed80bd3da10c3b
634b99b656cfefeafe4504c2ac1f9ddd
62112cf78affd879c8dcef2f3e62077f
fc11c9cb0d4433143271f0f767864a30
eeab715dc67af05280c926dc4c4676f5
Satori:
29ed147052e003024662a8ec53dbe3e7
fdbf35b0abe7d83289a5cb73b1ac6e56
977534e59c72dafd0160457d802f693d
27d6fb9b8af8408ca6ce2831762fa021
cc2e611a511d4d907a6d39f552cc81df
a4abd90ea1a1a93e2b813abd380eda94
ff06b2584f44e24b517074230c8de6e9
e8abfd033843b4504797eceaf825a118MMD (malwaremustdie.org), reversed, analyzed, rules coded by: @unixfreaxjp