Saturday, December 28, 2024
HomeBackdoorLinux Backdoor that Creates Fully Encrypted Reverse Shell and Attack Unsecured Linux...

Linux Backdoor that Creates Fully Encrypted Reverse Shell and Attack Unsecured Linux Systems

Published on

SIEM as a Service

A dangerous Linux backdoor Chaos that targeting improperly Secured Linux systems by using fully encrypted and integrity checked reverse shell.

Hackers performing  SSH brute-force attacks on Linux systems that secured by weak password and executing the Chaos Backdoor.

Chaos Backdoor was part of the  ‘sebd’ rootkit that was active around 2013 and now it is discovered via Honeypot system.

- Advertisement - SIEM as a Service

Initially, attackers compromised one of the honeypot systems by brute-forcing SSH credentials using Tor network.

Also Read:  Zero Day Attack Prevention: A Fundamental Pillar of Security

How does this Linux Backdoor Works

Attacker initially disabled the logging history an checked the SSHD binary to make sure the system did not compromise by any other attackers.

Most of the SSH attacks initiated by check the patched SSHDs to log stolen SSH credentials.

Attack initially download an image file that pretended to be a jpg from  http://xxx.xxx.xxx.29/cs/default2.jpg but the original file was distributed with .tar. so .jpg extension makes more legitimate for the victim to open it.

Chaos Backdoor that archived in .tar is the original backdoor that installed on the victim’s system and the “Client” file is the client to connect to the installed backdoor.

After installing into the Linux System and getting reverse shell, attacker distributing two files that is Chaos and Client. here, Chaos works as a backdoor and client will help to connect-back from chaos.

According to gosecure, It was interesting to see that both parties have the same two keys, which are used for sending and receiving. The encrypted password turned out to be hardcoded which we managed to crack and get the password in plain text. The password seems to be reused across different infections. 

This backdoor simply changed the name from e ‘sebd’ rootkit. and in this case, the original backdoor was stolen and used here by changing the name and make it believe it is a newly created backdoor.

The Chaos backdoor is pretty interesting as it uses a stealthy raw socket to spawn a reverse-shell with full network encryption and integrity checks. However, the backdoor’s encryption can easily be broken if the pre-shared key is known, as it is transmitted in clear text. concluded by gosecure.

IOC File Hashes

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Lumma Stealer Attacking Users To Steal Login Credentials From Browsers

Researchers observed Lumma Stealer activity across multiple online samples, including PowerShell scripts and a...

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...

Palo Alto Networks Vulnerability Puts Firewalls at Risk of DoS Attacks

A critical vulnerability, CVE-2024-3393, has been identified in the DNS Security feature of Palo...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

SMOKEDHAM Backdoor Mimic As Legitimate Tools Leveraging Google Drive & Dropbox

UNC2465, a financially motivated threat actor, leverages the SMOKEDHAM backdoor to gain initial access...

Rekoobe Backdoor In Open Directories Possibly Attacking TradingView Users

APT31, using the Rekoobe backdoor, has been observed targeting TradingView, a popular financial platform,...

Researchers Backdoored Azure Automation Account Packages And Runtime Environments

Runtime environments offer a flexible way to customize Automation Account Runbooks with specific packages....