Track Common Adversary Tasks Performed Using Bonadan

By Ashwin Venugopal -

 






To know more about it, you can go through my detailed document by clicking here





Overview

Bonadan is a malicious form of OpenSSH, which can also act as a custom backdoor. It was detected in 2018 and is a combination of new cryptocurrency-mining module and the same credential-stealing module generally used by the Onderon family of backdoors.

How Does It works?

The module used in this backdoor starts as a new thread that can periodically call two functions after every five minutes. The first one checks and removes any kind of cryptocurrency miner installed on the system, whereas the second one connects with the C&C server and sends the following information about the host:
  1. Username corresponding to the user running the backdoor.
  2. Version of the OS.
  3. External IP address of the infected host.
  4. CPU model.
  5. RAM size.
  6. Speed of the running miner., etc.  

Defense 

You can use the following methods to defend against the malware:
  • Use long and complex passwords.
  • Enable key-based authentications.
  • Disable remote root logins.
  • Use multi-factor Authentication through PAM (Pluggable Authentication Module).
  • Block all the IP addresses attempting brute force attacks with the help of available software.
  • Always update IDS/IPS in order to take proper action at the time of an incident.










To know more about it, you can go through my detailed document by clicking here






























Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more