Albabat Ransomware Group Potentially Expands Targets to Multiple OS, Uses GitHub to Streamline Opera
Summary:
New variants of the Albabat ransomware were recently discovered by researchers at Trend Micro, which now target not only Microsoft Windows systems but also gather hardware and system information from Linux and macOS environments. For its part, Albabat is capable of stealing a wide range of data from infected machines including system details, user information, geolocation data, encryption status and details regarding ransom payments. This data is further sent to a PostgreSQL database, enabling attackers to monitor the status of infections and ransom payments. Notably, the latest versions of Albabat, 2.0.0 and 2.5, are designed to retrieve their configuration data through GitHub’s REST API. These configurations provide detailed operational parameters for the malware, such as which files and directories to encrypt or exclude, including extensions like .exe, .mp3, .dat, .dll, and more. By using GitHub to retrieve these configurations, the ransomware group can easily update their malware's behavior without the need for direct communication with compromised systems.
Security Officer Comments:
The support for operating systems like Linux and macOS, indicates that the operators behind Albabat ransomware are looking to expand their targeting beyond Windows systems. Furthermore, the use of GitHub in Albabat’s operations is particularly noteworthy. According to Trend Micro, Albabat utilizes a private repository, billdev1[.]github[.]io, to store and distribute its ransomware configuration files. This allows the operators to make changes to the ransomware’s behavior in real time without raising suspicion. Trend Micro was able to access this repository using an authentication token discovered while capturing network traffic with Fiddler. The repository is associated with a user named "Bill Borguiann," who has made several commits to the repository since its creation last year, primarily focusing on modifying the configuration code. During their analysis, researchers identified a folder labeled "2.5.x," indicating a potential new version of the ransomware. While no binary for this newer version was found, the configuration file in the folder revealed the addition of new cryptocurrency wallets for Bitcoin, Ethereum, Solana, and BNB. Although no transactions have been detected in these wallets yet, it is highly likely they will be used to receive ransom payments from victims in future attacks.
Suggested Corrections:
Backup your data, system images, and configurations, regularly test them, and keep the backups offline: Ensure that backups are regularly tested and that they are not connected to the business network, as many ransomware variants try to find and encrypt or delete accessible backups. Maintaining current backups offline is critical because if your network data is encrypted with ransomware, your organization can restore systems.
Update and patch systems promptly: This includes maintaining the security of operating systems, applications, and firmware in a timely manner. Consider using a centralized patch management system; use a risk-based assessment strategy to drive your patch management program.
Test your incident response plan: There's nothing that shows the gaps in plans more than testing them. Run through some core questions and use those to build an incident response plan: Are you able to sustain business operations without access to certain systems? For how long? Would you turn off your manufacturing operations if business systems such as billing were offline?
Check your security team's work: Use a 3rd party pen tester to test the security of your systems and your ability to defend against a sophisticated attack. Many ransomware criminals are aggressive and sophisticated and will find the equivalent of unlocked doors.
Segment your networks: There's been a recent shift in ransomware attacks – from stealing data to disrupting operations. It's critically important that your corporate business functions and manufacturing/production operations are separated and that you carefully filter and limit internet access to operational networks, identify links between these networks, and develop workarounds or manual controls to ensure ICS networks can be isolated and continue operating if your corporate network is compromised. Regularly test contingency plans such as manual controls so that safety-critical functions can be maintained during a cyber incident.
Train employees:
Email remains the most vulnerable attack vector for organizations. Users should be trained on how to avoid and spot phishing emails. Multi-factor authentication can help prevent malicious access to sensitive services.
Implement multi-factor authentication (MFA):
External-facing assets that leverage single-factor authentication (SFA) are highly susceptible to brute-forcing attacks, password spraying, or unauthorized remote access using valid (stolen) credentials. Implementing MFA enhances security and adds an extra layer of protection.
Link(s):
https://www.trendmicro.com/en_hk/research/25/c/albabat-ransomware-group.html
New variants of the Albabat ransomware were recently discovered by researchers at Trend Micro, which now target not only Microsoft Windows systems but also gather hardware and system information from Linux and macOS environments. For its part, Albabat is capable of stealing a wide range of data from infected machines including system details, user information, geolocation data, encryption status and details regarding ransom payments. This data is further sent to a PostgreSQL database, enabling attackers to monitor the status of infections and ransom payments. Notably, the latest versions of Albabat, 2.0.0 and 2.5, are designed to retrieve their configuration data through GitHub’s REST API. These configurations provide detailed operational parameters for the malware, such as which files and directories to encrypt or exclude, including extensions like .exe, .mp3, .dat, .dll, and more. By using GitHub to retrieve these configurations, the ransomware group can easily update their malware's behavior without the need for direct communication with compromised systems.
Security Officer Comments:
The support for operating systems like Linux and macOS, indicates that the operators behind Albabat ransomware are looking to expand their targeting beyond Windows systems. Furthermore, the use of GitHub in Albabat’s operations is particularly noteworthy. According to Trend Micro, Albabat utilizes a private repository, billdev1[.]github[.]io, to store and distribute its ransomware configuration files. This allows the operators to make changes to the ransomware’s behavior in real time without raising suspicion. Trend Micro was able to access this repository using an authentication token discovered while capturing network traffic with Fiddler. The repository is associated with a user named "Bill Borguiann," who has made several commits to the repository since its creation last year, primarily focusing on modifying the configuration code. During their analysis, researchers identified a folder labeled "2.5.x," indicating a potential new version of the ransomware. While no binary for this newer version was found, the configuration file in the folder revealed the addition of new cryptocurrency wallets for Bitcoin, Ethereum, Solana, and BNB. Although no transactions have been detected in these wallets yet, it is highly likely they will be used to receive ransom payments from victims in future attacks.
Suggested Corrections:
Backup your data, system images, and configurations, regularly test them, and keep the backups offline: Ensure that backups are regularly tested and that they are not connected to the business network, as many ransomware variants try to find and encrypt or delete accessible backups. Maintaining current backups offline is critical because if your network data is encrypted with ransomware, your organization can restore systems.
Update and patch systems promptly: This includes maintaining the security of operating systems, applications, and firmware in a timely manner. Consider using a centralized patch management system; use a risk-based assessment strategy to drive your patch management program.
Test your incident response plan: There's nothing that shows the gaps in plans more than testing them. Run through some core questions and use those to build an incident response plan: Are you able to sustain business operations without access to certain systems? For how long? Would you turn off your manufacturing operations if business systems such as billing were offline?
Check your security team's work: Use a 3rd party pen tester to test the security of your systems and your ability to defend against a sophisticated attack. Many ransomware criminals are aggressive and sophisticated and will find the equivalent of unlocked doors.
Segment your networks: There's been a recent shift in ransomware attacks – from stealing data to disrupting operations. It's critically important that your corporate business functions and manufacturing/production operations are separated and that you carefully filter and limit internet access to operational networks, identify links between these networks, and develop workarounds or manual controls to ensure ICS networks can be isolated and continue operating if your corporate network is compromised. Regularly test contingency plans such as manual controls so that safety-critical functions can be maintained during a cyber incident.
Train employees:
Email remains the most vulnerable attack vector for organizations. Users should be trained on how to avoid and spot phishing emails. Multi-factor authentication can help prevent malicious access to sensitive services.
Implement multi-factor authentication (MFA):
External-facing assets that leverage single-factor authentication (SFA) are highly susceptible to brute-forcing attacks, password spraying, or unauthorized remote access using valid (stolen) credentials. Implementing MFA enhances security and adds an extra layer of protection.
Link(s):
https://www.trendmicro.com/en_hk/research/25/c/albabat-ransomware-group.html