Molerats APT

By Ashwin Venugopal -

 





Overview

Molerats malware is also known as ALUMINUM SARATOGA, Extreme Jackal, G0021, Gaza Cybergang, Gaza Hackers Team, Moonlight, and Operation Molerats. This malware mainly targeted the Middle East government institutions and global government organizations associated with geopolitics in the region. 

It is a type of Advanced Persistent Threat (APT) that is mostly interested in Israel and Palestine, along with the other regions in the Middle East. The custom malware implant of the threat actor allows reconnaissance on the victim and exfiltrate data. It can also leverage multiple mechanisms to avoid automated threat analysis including geofencing based on IP addresses, only target computers with Arabic language packs installed, and password-protected archive files to distribute malware.

Main Features

  • Uses open-source and commercial packers for the backdoor. 
  • Targets Middle East region.
  • Uses Dropbox API for entire C2 communication. 
  • Use RAR files for backdoor delivery as well as later stages.
  • Use other legit cloud hosting services like Google Drive to host the payloads.

Analysis

This threat actor is using the malware LastConn,an updated version or new variant of SharpStage, in its recent campaigns that are email-based.  The malware especially targets the computers with Arabic language installed pack to ensure the desired targets. It is an actively developed and maintained malware, that uses Dropbox for all C2 capabilities and infrastructure. It also consists of multiple qualities that can prevent both automated and manual malware analysis.

Conclusion

Molerats is a highly effective and capable threat actor especially for those working with the government and other geopolitical entities in the Middle East. Evidently, it will continue to develop and modify customized malware implants to evade detection and automated analysis. Hence, to protect against such threat actor, it is advisable to carefully download and open any password protected archives, and open them from trusted sources only. 



































































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