Track Common Adversary Tasks Performed Using Aria-body

By Ashwin Venugopal -

 







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







Overview

Aria-body is a backdoor extensively used by Naikon APT, a Chinese-speaking adversary since 2017 and make use of the victim's infrastructure to attack the other targets. They generally targets Government-owned companies as well as the ministries of foreign affairs, science and technology of various countries like Australia, the Philippines, Vietnam, Thailand, Myanmar, Brunei, etc. There attacks have increased since 2019 with the help of the other APTs, and their victims' network serves as the command and control (C2) server.

Techniques & Tactics

Aria-body backdoor follows following pattern:
  • Firstly, it pose its email and document as an official government one with the required information for the target (which is generally the data stolen from the other compromised systems).

  • Then, it adds a downloader to the document for Aria-body in order to gain access to the target's network.

  • After the successful completion of the above steps, it starts to make use of the victim's own servers to continue its attack against the other targets of interest.

Prevention

In order to secure your network from this malware, you have to perform following tasks:
  • Don't open any kind of unknown, suspicious, and irrelevant mails as this may compromise your system. 

  • It is also recommended to use only Microsoft Office versions released after 2010.

  • Downloads must only be done from official and verified sources.

  • Install a reputable anti-virus/anti-spyware suite, which must be updated timely. 











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