Edit tour

Linux Analysis Report
fenty.arm4.elf

Overview

General Information

Sample name:	fenty.arm4.elf
Analysis ID:	1587263
MD5:	3da78d3e972e8037746bd25fc180f60d
SHA1:	35bbe8c413fca2ff8d35c911953f7411c74feb79
SHA256:	98b8766cd8476480b19ae070e61b18e9fa688e38d7e25b2123fad819f22da0e1
Tags:	elfuser-abuse_ch
Infos:

Detection

Mirai

Score:	72
Range:	0 - 100
Whitelisted:	false

Signatures

Malicious sample detected (through community Yara rule)

Multi AV Scanner detection for submitted file

Yara detected Mirai

Sample deletes itself

Sample is packed with UPX

Detected TCP or UDP traffic on non-standard ports

ELF contains segments with high entropy indicating compressed/encrypted content

Enumerates processes within the "proc" file system

Sample contains only a LOAD segment without any section mappings

Sample listens on a socket

Sample tries to kill a process (SIGKILL)

Tries to connect to HTTP servers, but all servers are down (expired dropper behavior)

Uses the "uname" system call to query kernel version information (possible evasion)

Yara signature match

Classification

General Information

Joe Sandbox version:	42.0.0 Malachite
Analysis ID:	1587263
Start date and time:	2025-01-10 01:52:08 +01:00
Joe Sandbox product:	CloudBasic
Overall analysis duration:	0h 4m 22s
Hypervisor based Inspection enabled:	false
Report type:	full
Cookbook file name:	defaultlinuxfilecookbook.jbs
Analysis system description:	Ubuntu Linux 20.04 x64 (Kernel 5.4.0-72, Firefox 91.0, Evince Document Viewer 3.36.10, LibreOffice 6.4.7.2, OpenJDK 11.0.11)
Analysis Mode:	default
Sample name:	fenty.arm4.elf
Detection:	MAL
Classification:	mal72.troj.evad.linELF@0/0@0/0

Runtime Messages

Command:	/tmp/fenty.arm4.elf
PID:	5431
Exit Code:	0
Exit Code Info:
Killed:	False
Standard Output:	Hello, World!
Standard Error:

Process Tree

system is lnxubuntu20

fenty.arm4.elf (PID: 5431, Parent: 5355, MD5: 5ebfcae4fe2471fcc5695c2394773ff1) Arguments: /tmp/fenty.arm4.elf

fenty.arm4.elf New Fork (PID: 5433, Parent: 5431)

fenty.arm4.elf New Fork (PID: 5435, Parent: 5433)

fenty.arm4.elf New Fork (PID: 5437, Parent: 5433)

gnome-session-binary New Fork (PID: 5439, Parent: 1588)

sh (PID: 5439, Parent: 1588, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /bin/sh -e -u -c "export GIO_LAUNCHED_DESKTOP_FILE_PID=$$; exec \"$@\"" sh /usr/libexec/gsd-housekeeping

gsd-housekeeping (PID: 5439, Parent: 1588, MD5: b55f3394a84976ddb92a2915e5d76914) Arguments: /usr/libexec/gsd-housekeeping

cleanup

Malware Threat Intel

Provided by

Name	Description	Attribution	Blogpost URLs	Link
Mirai	Mirai is one of the first significant botnets targeting exposed networking devices running Linux. Found in August 2016 by MalwareMustDie, its name means "future" in Japanese. Nowadays it targets a wide range of networked embedded devices such as IP cameras, home routers (many vendors involved), and other IoT devices. Since the source code was published on "Hack Forums" many variants of the Mirai family appeared, infecting mostly home networks all around the world.	No Attribution	http://osint.bambenekconsulting.com/feeds/ http://www.simonroses.com/2016/10/mirai-ddos-botnet-source-code-binary-analysis/ https://blog.malwaremustdie.org/2020/02/mmd-0065-2021-linuxmirai-fbot-re.html https://blog.netlab.360.com/another-lilin-dvr-0-day-being-used-to-spread-mirai-en/ https://blog.netlab.360.com/mirai_ptea-botnet-is-exploiting-undisclosed-kguard-dvr-vulnerability-en/	https://malpedia.caad.fkie.fraunhofer.de/details/elf.mirai

Yara Signatures

Memory Dumps

Source	Rule	Description	Author	Strings
5431.1.00007f7410017000.00007f7410029000.r-x.sdmp	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
5431.1.00007f7410017000.00007f7410029000.r-x.sdmp	Mirai_Botnet_Malware	Detects Mirai Botnet Malware	Florian Roth	0x1018c:$x2: /dev/misc/watchdog 0x1017c:$x3: /dev/watchdog 0x101c8:$x3: /dev/watchdog 0x1033c:$s1: LCOGQGPTGP

Joe Sandbox Signatures

Click to jump to signature section

Show All Signature Results

AV Detection

Multi AV Scanner detection for submitted file

Source: fenty.arm4.elf

ReversingLabs: Detection: 21%

Source: global traffic

TCP traffic: 192.168.2.13:46646 -> 185.196.9.234:2969

Source: /tmp/fenty.arm4.elf (PID: 5431)

Socket: 0.0.0.0:54721

Jump to behavior

Source: global traffic

TCP traffic: 192.168.2.13:48202 -> 185.125.190.26:443

Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.125.190.26
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.125.190.26
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234
Source: unknown	TCP traffic detected without corresponding DNS query: 185.196.9.234

Source: fenty.arm4.elf

String found in binary or memory: http://upx.sf.net

Source: unknown

Network traffic detected: HTTP traffic on port 48202 -> 443

System Summary

Malicious sample detected (through community Yara rule)

Source: 5431.1.00007f7410017000.00007f7410029000.r-x.sdmp, type: MEMORY

Matched rule: Detects Mirai Botnet Malware Author: Florian Roth

Source: LOAD without section mappings

Program segment: 0x8000

Source: /tmp/fenty.arm4.elf (PID: 5437)	SIGKILL sent: pid: 792, result: successful	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5437)	SIGKILL sent: pid: 884, result: successful	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5437)	SIGKILL sent: pid: 1944, result: successful	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5437)	SIGKILL sent: pid: 3181, result: successful	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5437)	SIGKILL sent: pid: 3185, result: successful	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5437)	SIGKILL sent: pid: 5439, result: successful	Jump to behavior

Source: 5431.1.00007f7410017000.00007f7410029000.r-x.sdmp, type: MEMORY

Matched rule: Mirai_Botnet_Malware date = 2016-10-04, hash5 = 420bf9215dfb04e5008c5e522eee9946599e2b323b17f17919cd802ebb012175, hash4 = 2efa09c124f277be2199bee58f49fc0ce6c64c0bef30079dfb3d94a6de492a69, hash3 = 20683ff7a5fec1237fc09224af40be029b9548c62c693844624089af568c89d4, hash2 = 05c78c3052b390435e53a87e3d31e9fb17f7c76bb4df2814313bca24735ce81c, hash1 = 05c78c3052b390435e53a87e3d31e9fb17f7c76bb4df2814313bca24735ce81c, author = Florian Roth, description = Detects Mirai Botnet Malware, hash10 = c61bf95146c68bfbbe01d7695337ed0e93ea759f59f651799f07eecdb339f83f, hash11 = d9573c3850e2ae35f371dff977fc3e5282a5e67db8e3274fd7818e8273fd5c89, hash12 = f1100c84abff05e0501e77781160d9815628e7fd2de9e53f5454dbcac7c84ca5, hash9 = bf0471b37dba7939524a30d7d5afc8fcfb8d4a7c9954343196737e72ea4e2dc4, hash8 = 89570ae59462e6472b6769545a999bde8457e47ae0d385caaa3499ab735b8147, hash7 = 70bb0ec35dd9afcfd52ec4e1d920e7045dc51dca0573cd4c753987c9d79405c0, hash6 = 62cdc8b7fffbaf5683a466f6503c03e68a15413a90f6afd5a13ba027631460c6, reference = Internal Research, license = https://creativecommons.org/licenses/by-nc/4.0/, hash13 = fb713ccf839362bf0fbe01aedd6796f4d74521b133011b408e42c1fd9ab8246b

Source: classification engine

Classification label: mal72.troj.evad.linELF@0/0@0/0

Data Obfuscation

Sample is packed with UPX

Source: initial sample	String containing UPX found: $Info: This file is packed with the UPX executable packer http://upx.sf.net $
Source: initial sample	String containing UPX found: $Info: This file is packed with the UPX executable packer http://upx.sf.net $
Source: initial sample	String containing UPX found: $Id: UPX 3.94 Copyright (C) 1996-2017 the UPX Team. All Rights Reserved. $

Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/5380/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/230/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/110/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/231/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/111/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/232/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/112/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/233/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/113/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/234/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/114/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/235/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/115/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/236/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/116/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/237/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/117/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/238/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/118/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/239/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/119/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/914/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/10/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/917/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/11/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/12/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/13/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/5274/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/14/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/15/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/16/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/17/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/18/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/19/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/240/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/3095/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/120/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/241/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/121/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/242/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/1/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/122/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/243/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/2/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/123/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/244/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/3/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/124/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/245/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/1588/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/125/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/4/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/246/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/126/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/5/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/247/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/127/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/6/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/248/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/128/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/7/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/249/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/129/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/8/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/800/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/3762/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/9/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/1906/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/802/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/803/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/20/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/21/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/22/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/23/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/24/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/25/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/26/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/27/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/28/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/29/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/3420/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/1482/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/490/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/1480/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/250/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/371/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/130/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/251/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/131/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/252/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/132/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/253/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/254/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/1238/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/134/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/255/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/256/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/257/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/378/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/3413/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/258/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/259/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/1475/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/936/cmdline	Jump to behavior
Source: /tmp/fenty.arm4.elf (PID: 5435)	File opened: /proc/30/cmdline	Jump to behavior

Hooking and other Techniques for Hiding and Protection

Sample deletes itself

Source: /tmp/fenty.arm4.elf (PID: 5431)

File: /tmp/fenty.arm4.elf

Jump to behavior

Source: fenty.arm4.elf

Submission file: segment LOAD with 7.7445 entropy (max. 8.0)

Source: /tmp/fenty.arm4.elf (PID: 5431)

Queries kernel information via 'uname':

Jump to behavior

Source: fenty.arm4.elf, 5431.1.000055e942cd5000.000055e942e63000.rw-.sdmp	Binary or memory string: U!/etc/qemu-binfmt/arm
Source: fenty.arm4.elf, 5431.1.000055e942cd5000.000055e942e63000.rw-.sdmp	Binary or memory string: /etc/qemu-binfmt/arm
Source: fenty.arm4.elf, 5431.1.00007ffe367a9000.00007ffe367ca000.rw-.sdmp	Binary or memory string: /usr/bin/qemu-arm
Source: fenty.arm4.elf, 5431.1.00007ffe367a9000.00007ffe367ca000.rw-.sdmp	Binary or memory string: x86_64/usr/bin/qemu-arm/tmp/fenty.arm4.elfSUDO_USER=saturninoPATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/binDISPLAY=:1.0XAUTHORITY=/run/user/1000/gdm/XauthoritySUDO_UID=1000TERM=xterm-256colorCOLORTERM=truecolorLOGNAME=rootUSER=rootLANG=en_US.UTF-8SUDO_COMMAND=/bin/bashHOME=/rootMAIL=/var/mail/rootSUDO_GID=1000SHELL=/bin/bash/tmp/fenty.arm4.elf

Stealing of Sensitive Information

Yara detected Mirai

Source: Yara match

File source: 5431.1.00007f7410017000.00007f7410029000.r-x.sdmp, type: MEMORY

Remote Access Functionality

Yara detected Mirai

Source: Yara match

File source: 5431.1.00007f7410017000.00007f7410029000.r-x.sdmp, type: MEMORY

Mitre Att&ck Matrix

Reconnaissance	Resource Development	Initial Access	Execution	Persistence	Privilege Escalation	Defense Evasion	Credential Access	Discovery	Lateral Movement	Collection	Command and Control	Exfiltration	Impact
Gather Victim Identity Information	Acquire Infrastructure	Valid Accounts	Windows Management Instrumentation	Path Interception	Path Interception	11 Obfuscated Files or Information	1 OS Credential Dumping	11 Security Software Discovery	Remote Services	Data from Local System	1 Encrypted Channel	Exfiltration Over Other Network Medium	Abuse Accessibility Features
Credentials	Domains	Default Accounts	Scheduled Task/Job	Boot or Logon Initialization Scripts	Boot or Logon Initialization Scripts	1 File Deletion	LSASS Memory	Application Window Discovery	Remote Desktop Protocol	Data from Removable Media	1 Non-Standard Port	Exfiltration Over Bluetooth	Network Denial of Service
Email Addresses	DNS Server	Domain Accounts	At	Logon Script (Windows)	Logon Script (Windows)	Obfuscated Files or Information	Security Account Manager	Query Registry	SMB/Windows Admin Shares	Data from Network Shared Drive	1 Application Layer Protocol	Automated Exfiltration	Data Encrypted for Impact

Malware Configuration

⊘No configs have been found

Behavior Graph

Hide Legend

Legend:

Process
Signature
Created File
DNS/IP Info
Is Dropped
Number of created Files
Is malicious
Internet

Source	Detection	Scanner	Label	Link
fenty.arm4.elf	21%	ReversingLabs	Linux.Trojan.Mirai

Name	Source	Malicious	Antivirus Detection	Reputation
http://upx.sf.net	fenty.arm4.elf	false		high

World Map of Contacted IPs

No. of IPs < 25%
25% < No. of IPs < 50%
50% < No. of IPs < 75%
75% < No. of IPs

Public IPs

IP	Domain	Country	Flag	ASN	ASN Name	Malicious
185.125.190.26	unknown	United Kingdom		41231	CANONICAL-ASGB	false
185.196.9.234	unknown	Switzerland		42624	SIMPLECARRIERCH	false

Joe Sandbox View / Context

IPs

Match	Associated Sample Name / URL	SHA 256	Detection	Threat Name	Link
185.125.190.26	Space.x86.elf	Get hash	malicious	Unknown	Browse
	boatnet.mpsl.elf	Get hash	malicious	Mirai	Browse
	wind.arm5.elf	Get hash	malicious	Mirai	Browse
	main_ppc.elf	Get hash	malicious	Mirai	Browse
	.i.elf	Get hash	malicious	Unknown	Browse
	main_x86.elf	Get hash	malicious	Mirai	Browse
	mips.elf	Get hash	malicious	Mirai	Browse
	ssh.elf	Get hash	malicious	Mirai, Gafgyt	Browse
	army6.elf	Get hash	malicious	Gafgyt, Mirai	Browse
	boatnet.arm6.elf	Get hash	malicious	Mirai	Browse
185.196.9.234	fenty.arm7.elf	Get hash	malicious	Mirai	Browse
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse

Domains

⊘No context

ASNs

Match	Associated Sample Name / URL	SHA 256	Detection	Threat Name	Link	Context
SIMPLECARRIERCH	fenty.arm7.elf	Get hash	malicious	Mirai	Browse	185.196.9.234
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse	185.196.9.234
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse	185.196.9.234
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse	185.196.9.234
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse	185.196.9.234
	fenty.arm5.elf	Get hash	malicious	Mirai	Browse	185.196.9.234
	sparc.elf	Get hash	malicious	Mirai	Browse	185.196.10.127
	armv6l.elf	Get hash	malicious	Mirai	Browse	185.196.10.127
	sh4.elf	Get hash	malicious	Mirai	Browse	185.196.10.127
	mips.elf	Get hash	malicious	Mirai	Browse	185.196.10.127
CANONICAL-ASGB	fenty.arm7.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	armv4eb.elf	Get hash	malicious	Unknown	Browse	91.189.91.42
	Space.x86.elf	Get hash	malicious	Unknown	Browse	185.125.190.26
	12.elf	Get hash	malicious	Unknown	Browse	91.189.91.42
	2.elf	Get hash	malicious	Unknown	Browse	91.189.91.42
	fenty.arm7.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	fenty.arm6.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	wind.x86.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	wind.ppc.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	arm.elf	Get hash	malicious	Unknown	Browse	91.189.91.42

File type:	ELF 32-bit LSB executable, ARM, version 1 (ARM), statically linked, no section header
Entropy (8bit):	7.741372959778678
TrID:	ELF Executable and Linkable format (generic) (4004/1) 100.00%
File name:	fenty.arm4.elf
File size:	33'668 bytes
MD5:	3da78d3e972e8037746bd25fc180f60d
SHA1:	35bbe8c413fca2ff8d35c911953f7411c74feb79
SHA256:	98b8766cd8476480b19ae070e61b18e9fa688e38d7e25b2123fad819f22da0e1
SHA512:	80399e4cb240bfec064f195967a171390ae856125364e1aea7b96b7653430e0f61444e2085852ba1685b21993b3d8c0ef5ab871b4a2c1b856fdd1deae129b3ed
SSDEEP:	768:X6CfcrIcAv7xFuX3KO6iuhrnCs1QR8hRnngJ9f3ykddRN:X6ocjAzxFgv6iuheRqEf3ykTRN
TLSH:	0EE2E19DF1B01A56C60A047290FDD9F7AE2F77EA1586A3AC6C508027FC2D4C79767C44
File Content Preview:	.ELF...a..........(.....P...4...........4. ...(..........................................8...8...8..................Q.td............................~..vUPX!X.......t...t.......[.........ELF.ra....(........4.....[... ..............8..6.....<.l...h.....%...

Static ELF Info

ELF header
Class:	ELF32
Data:	2's complement, little endian
Version:	1 (current)
Machine:	ARM
Version Number:	0x1
Type:	EXEC (Executable file)
OS/ABI:	ARM - ABI
ABI Version:	0
Entry Point Address:	0xf950
Flags:	0x202
ELF Header Size:	52
Program Header Offset:	52
Program Header Size:	32
Number of Program Headers:	3
Section Header Offset:	0
Section Header Size:	40
Number of Section Headers:	0
Header String Table Index:	0

Program Segments

Type	Offset	Virtual Address	Physical Address	File Size	Memory Size	Entropy	Flags	Flags Description	Align
LOAD	0x0	0x8000	0x8000	0x828b	0x828b	7.7445	0x5	R E	0x8000
LOAD	0x38f4	0x238f4	0x238f4	0x0	0x0	0.0000	0x6	RW	0x8000
GNU_STACK	0x0	0x0	0x0	0x0	0x0	0.0000	0x7	RWE	0x4

Timestamp	Source Port	Dest Port	Source IP	Dest IP
Jan 10, 2025 01:52:49.641057014 CET	46646	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:49.646027088 CET	2969	46646	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:49.646070004 CET	46646	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:49.659768105 CET	46646	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:49.664705992 CET	2969	46646	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:49.664756060 CET	46646	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:49.669656038 CET	2969	46646	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:50.302458048 CET	2969	46646	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:50.302504063 CET	46646	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.302675962 CET	46646	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.303356886 CET	46648	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.308182955 CET	2969	46648	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:50.308248043 CET	46648	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.309756041 CET	46648	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.314538956 CET	2969	46648	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:50.314604044 CET	46648	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.319355011 CET	2969	46648	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:50.990726948 CET	2969	46648	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:50.990915060 CET	46648	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.990915060 CET	46648	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.991353035 CET	46650	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.996248960 CET	2969	46650	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:50.996330023 CET	46650	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:50.997061968 CET	46650	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:51.002171993 CET	2969	46650	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:51.002235889 CET	46650	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:52:51.007117987 CET	2969	46650	185.196.9.234	192.168.2.13
Jan 10, 2025 01:52:59.042937040 CET	48202	443	192.168.2.13	185.125.190.26
Jan 10, 2025 01:53:01.007282972 CET	46650	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:53:01.012375116 CET	2969	46650	185.196.9.234	192.168.2.13
Jan 10, 2025 01:53:01.213701963 CET	2969	46650	185.196.9.234	192.168.2.13
Jan 10, 2025 01:53:01.213890076 CET	46650	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:53:30.019037008 CET	48202	443	192.168.2.13	185.125.190.26
Jan 10, 2025 01:54:01.269583941 CET	46650	2969	192.168.2.13	185.196.9.234
Jan 10, 2025 01:54:01.275069952 CET	2969	46650	185.196.9.234	192.168.2.13
Jan 10, 2025 01:54:01.476265907 CET	2969	46650	185.196.9.234	192.168.2.13
Jan 10, 2025 01:54:01.476739883 CET	46650	2969	192.168.2.13	185.196.9.234

System Behavior

Analysis Process: fenty.arm4.elf PID: 5431, Parent PID: 5355

General

Start time (UTC):	00:52:49
Start date (UTC):	10/01/2025
Path:	/tmp/fenty.arm4.elf
Arguments:	/tmp/fenty.arm4.elf
File size:	4956856 bytes
MD5 hash:	5ebfcae4fe2471fcc5695c2394773ff1

Start time (UTC):	00:52:49
Start date (UTC):	10/01/2025
Path:	/tmp/fenty.arm4.elf
Arguments:	-
File size:	4956856 bytes
MD5 hash:	5ebfcae4fe2471fcc5695c2394773ff1

Start time (UTC):	00:52:49
Start date (UTC):	10/01/2025
Path:	/tmp/fenty.arm4.elf
Arguments:	-
File size:	4956856 bytes
MD5 hash:	5ebfcae4fe2471fcc5695c2394773ff1

Start time (UTC):	00:52:49
Start date (UTC):	10/01/2025
Path:	/tmp/fenty.arm4.elf
Arguments:	-
File size:	4956856 bytes
MD5 hash:	5ebfcae4fe2471fcc5695c2394773ff1

Start time (UTC):	00:52:49
Start date (UTC):	10/01/2025
Path:	/usr/libexec/gnome-session-binary
Arguments:	-
File size:	334664 bytes
MD5 hash:	d9b90be4f7db60cb3c2d3da6a1d31bfb

Start time (UTC):	00:52:49
Start date (UTC):	10/01/2025
Path:	/bin/sh
Arguments:	/bin/sh -e -u -c "export GIO_LAUNCHED_DESKTOP_FILE_PID=$$; exec \"$@\"" sh /usr/libexec/gsd-housekeeping
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Start time (UTC):	00:52:49
Start date (UTC):	10/01/2025
Path:	/usr/libexec/gsd-housekeeping
Arguments:	/usr/libexec/gsd-housekeeping
File size:	51840 bytes
MD5 hash:	b55f3394a84976ddb92a2915e5d76914

Description:	Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.
Tactics:	Defense Evasion
Data Sources:	Command: Command Execution, File: File Creation, File: File Metadata, Module: Module Load, Process: OS API Execution, Process: Process Creation, Script: Script Execution, WMI: WMI Creation, Windows Registry: Windows Registry Key Creation
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may delete files left behind by the actions of their intrusion activity. Malware, tools, or other non-native files dropped or created on a system by an adversary (ex: Ingress Tool Transfer ) may leave traces to indicate to what was done within a network and how. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary's footprint.
Tactics:	Defense Evasion
Data Sources:	Command: Command Execution, File: File Deletion
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password, from the operating system and software. Credentials can then be used to perform Lateral Movement and access restricted information.
Tactics:	Credential Access
Data Sources:	Active Directory: Active Directory Object Access, Command: Command Execution, File: File Access, Network Traffic: Network Traffic Content, Network Traffic: Network Traffic Flow, Process: OS API Execution, Process: Process Access, Process: Process Creation, Windows Registry: Windows Registry Key Access
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may attempt to get a listing of security software, configurations, defensive tools, and sensors that are installed on a system or in a cloud environment. This may include things such as firewall rules and anti-virus. Adversaries may use the information from Security Software Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.
Tactics:	Discovery
Data Sources:	Command: Command Execution, Firewall: Firewall Enumeration, Firewall: Firewall Metadata, Process: OS API Execution, Process: Process Creation
Platforms:	Azure AD, Google Workspace, IaaS, Linux, macOS, Office 365, SaaS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may employ a known encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol. Despite the use of a secure algorithm, these implementations may be vulnerable to reverse engineering if secret keys are encoded and/or generated within malware samples/configuration files.
Tactics:	Command and Control
Data Sources:	Network Traffic: Network Traffic Content
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may communicate using a protocol and port pairing that are typically not associated. For example, HTTPS over port 8088or port 587as opposed to the traditional port 443. Adversaries may make changes to the standard port used by a protocol to bypass filtering or muddle analysis/parsing of network data.
Tactics:	Command and Control
Data Sources:	Network Traffic: Network Traffic Content, Network Traffic: Network Traffic Flow
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may communicate using OSI application layer protocols to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.
Tactics:	Command and Control
Data Sources:	Network Traffic: Network Traffic Content, Network Traffic: Network Traffic Flow
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Behavior Section

Behavior Chronological

Disassembly

Uncategorized

Graph

Loading Joe Sandbox Report ...

Warning!

Linux Analysis Report fenty.arm4.elf

Overview

General Information

Detection

Signatures

Classification

General Information

Runtime Messages

Process Tree

Malware Threat Intel

Yara Signatures

Memory Dumps

Suricata Signatures

Joe Sandbox Signatures

AV Detection

Networking

System Summary

Data Obfuscation

Persistence and Installation Behavior

Hooking and other Techniques for Hiding and Protection

Malware Analysis System Evasion

Stealing of Sensitive Information

Remote Access Functionality

Mitre Att&ck Matrix

Malware Configuration

Behavior Graph

Screenshots

Thumbnails

Antivirus, Machine Learning and Genetic Malware Detection

Initial Sample

Dropped Files

Domains

URLs

Domains and IPs

Contacted Domains

URLs from Memory and Binaries

World Map of Contacted IPs

Public IPs

Joe Sandbox View / Context

IPs

Domains

ASNs

JA3 Fingerprints

Dropped Files

Created / dropped Files

Static File Info

General

Static ELF Info

ELF header

Program Segments

Network Behavior

Network Port Distribution

TCP Packets

System Behavior

Analysis Process: fenty.arm4.elf PID: 5431, Parent PID: 5355

General

Chronological Activities

Analysis Process: fenty.arm4.elf PID: 5433, Parent PID: 5431

General

Chronological Activities

Analysis Process: fenty.arm4.elf PID: 5435, Parent PID: 5433

General

Chronological Activities

Analysis Process: fenty.arm4.elf PID: 5437, Parent PID: 5433

General

Chronological Activities

Analysis Process: gnome-session-binary PID: 5439, Parent PID: 1588

General

Chronological Activities

Analysis Process: sh PID: 5439, Parent PID: 1588

General

Chronological Activities

Analysis Process: gsd-housekeeping PID: 5439, Parent PID: 1588

Linux Analysis Report
fenty.arm4.elf