Track Common Adversary Tasks Performed Using BLUELIGHT

By Ashwin Venugopal -

 





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







Overview

BLUELIGHT is a Remote Access Trojan (RAT), generally used by APT37 (recently in 2021) which is a North-Korean state-sponsored cyber threat group that mainly targets the South-Korean public and private sectors including Japan, Vietnam, and the Middle East. It has targeted many industries like chemicals, electronics, manufacturing, aerospace, healthcare, etc. 

Cyber Attacks 

These cyber threat actors have targeted various South Korean sectors with RokRat Trojan, targets journalists using Chinotto multi-platform malware, etc. while focusing on the various sophisticated organizations of the attacked country.

Other Malware Tools used by APT37

APT37 is laced with a wide variety of malicious tools like NavRAT, CORALDECK, Karae, DOGCALL, ROKRAT, ScarCruft, SOUNDWAVE, ZUMKONG, MILKDRO, etc. which is capable of causing a big damage to any system or organization. 

Vulnerabilities Exploited 

  • Exploits vulnerabilities in Hangul Word Processor (HWP), and Adobe Flash.
  • Access zero-day vulnerabilities and use them in their operations.
  • Its InkySquids can easily infect the victims with Browser exploits., etc...

Prevention

All-in-all although they are not one of the topmost cyber threat groups, but organizations should be wary of them as they are very much capable in causing lethal damages to any company. You should - always keep track of all the passwords especially during peak hours, provide rigorous training to your employees regarding data security, always be careful about new logins and act swiftly whenever warned by your system regarding any breach, etc...








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