Understanding Attacks Linked to APT32

By Ashwin Venugopal -

 






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







Overview

APT32 or OceanLotus is a Vietnamese hacker group famous for targeting political dissidents, government officials, and businesses linked with Vietnam. It had reportedly attacked Ministry of Emergency Management as well as the Wuhan Municipal government of China in 2020 to obtain information about Covid-19 pandemic. 

APT32 also spreads malware via Google Play Store, fake news websites, facebook pages and also launches spyware attacks on Vietnamese Human Rights Activists.

APT32 Targets on Private Companies

  • A European corporation was attacked in 2014 before constructing a manufacturing facility in Vietnam.

  • Some of the Vietnamese as well as foreign companies related to network security, technology infrastructure, banking, media, etc. were compromised in 2016. 

  • A Global hospitality industry developer networks (partnering-up with Vietnam) were attacked in mid-2016.

  • Two other subsidiaries of U.S.A. and the Philippines consumer products were attack between 2016 and 2017.

APT32 Attacks on Government Sector

  • Various journalists, dissidents, activists, and bloggers were always a common targets of APT32 operations.

  • A security research division of Chinese firm Qihoo 360, was attacked in 2015 by APT32.

  • Two other Vietnamese media outlets were also attacked with APT32 malware between 2015 and 2016.

  • Members of the Vietnam diaspora in Australia and government officials in the Philippines were also targeted by APT32 in 2017.

APT32 Attack Tactics

APT32 always attacks stealthily on their targets;
  • It may use a privilege escalation exploit masquerading as a Window hotfix.

  • During one of the investigations, APT32 deployed its malware as a software deployment task in which all the systems pulled their payload from the same server.

  • It may also use some hidden or non-printing characters to visually camouflage its malware on a system.   














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

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...
Read more