Track Common Adversary Tasks Performed Using AppleSeed

By Ashwin Venugopal -

 





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









Overview

Appleseed is a type of backdoor extensively used by the North Korean threat actors Kimsuky APT (also knows as Thallium, Black Banshee, and Velvet Chollima) to mainly target South Korean government, academic, and commercial sectors since at least 2021. It make use of phishing websites, malicious documents, and scripts to target high profile people in South Korea government.

How Does It Works?

This backdoor generally uses two layer command structure in order to communicate to its command and control server i.e. the first one is the type of command that's required to be executed on the victim, and the second one is only used when the first layer is in upload data mode as well as defines the type of upload. AppleSeed mainly targets the South Korean government people like:
  • Ministry of Foreign Affairs, Republic of Korea First Secretary
  • Ministry of Foreign Affairs, Republic of Korea Second Secretary
  • Trade Minister
  • Deputy Consul General at Korean Consulate General in Hong Kong
  • International Atomic Energy Agency (IAEA) Nuclear Security Officer
  • Ambassador of the Embassy of Sri Lanka to the State
  • Minister of Foreign Affairs and Trade Counselor   

It has also extracted information about various South Korean Universities and companies like Seoul National University, Daishin Financial security company, KISA, etc. After successfully launching itself into the network, AppleSeed can steal following information:

  • Basic PC information such as PC name, OS version, processor, memory, etc.
  • User account credentials
  • Network information like IP address, routing table, port usage information, ARP list, etc.
  • List of running processes as well as services
  • Folders and files within Program Files, Programs in the Start menu, and List of recent files, etc.

This backdoor receives commands from the C2 server in order to download and run extra modules or perform whatever task the attacker wish to do.


Remedy

It is highly recommended to patch your public-facing network and use Mimikatz defense guide along with the other defensive techniques in order to improve your defensive stance as well as minimize its impact to your various operations. 















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 groups of computers, re
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 of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more