company logo

Product

Our Product

We are Reshaping the way Developers find and fix vulnerabilities before they get exploited.

Solutions

By Industry

BFSI

Healthcare

Education

IT & Telecom

Government

By Role

CISO/CTO

DevOps Engineer

Resources

Resource Library

Get actionable insight straight from our threat Intel lab to keep you informed about the ever-changing Threat landscape.

Subscribe to Our Weekly Threat Digest

Company

Contact Us

Have queries, feedback or prospects? Get in touch and we shall be with you shortly.

loading..
loading..
loading..
Loading...

Cloudflare

Volumetric DDoS

Botnet

loading..
loading..
loading..

Cloudflare employees also become victims of Twilio SMS phishing attack

Hackers behind the Twilio SMS phishing attack have also targeted employees of Cloudflare; however, they couldn't successfully obtain access…

09-Aug-2022
3 min read

Related Articles

loading..

macOS

Flutter

Discover how DPRK-backed actors use Flutter apps to bypass Apple security and ta...

A newly discovered macOS app, linked to DPRK, conceals sophisticated malware designed to breach system defenses. The malware uses advanced obfuscation tactics, such as packing the code and encrypting certain components, to evade detection. This campaign, discovered by Jamf Threat Labs, highlights the evolving threat posed by DPRK-backed actors, who often target sensitive data and use techniques such as social engineering and code obfuscation. This advanced persistent threat (APT) utilizes Flutter-built applications. Flutter's inherent obfuscation capabilities make it highly effective at evading detection. Features like hiding dynamic library calls and obscuring code flow complicate the analysis process, effectively aiding in concealing malicious activity. The findings mark a concerning escalation in novel methodologies used to breach macOS defenses, including cross-platform tools and techniques to bypass Apple notarization. ### DPRK Targets macOS Using Flutter-Built Malware In October, Jamf Threat Labs detected several malware samples uploaded to VirusTotal, a widely used malware analysis platform, that initially evaded detection despite exhibiting malicious behavior. Analysis of these samples pointed toward DPRK actors, with techniques aligning closely with previously observed malware campaigns. Disturbingly, some malware versions had even managed to pass Apple's notarization process temporarily, indicating sophisticated obfuscation and manipulation tactics. ### Complexity of the Flutter Packaging The malware was discovered in three different packaging forms: Go, Python, and Flutter. Among these, the Flutter variant stood out due to its complexity in reversing and analysis. Flutter, a cross-platform framework developed by Google, is typically used for consistent app design across platforms like macOS, iOS, and Android. For legitimate developers, Flutter's ability to write once and deploy across multiple platforms saves significant development time and resources, making it an attractive option. These same benefits also appeal to attackers, as they can create malware with broader reach and less effort. For example, popular apps like Google Ads and Alibaba are built using Flutter, demonstrating its versatility for creating high-performance cross-platform solutions. Its cross-platform capabilities are appealing to attackers because they can create malware that works across multiple operating systems with minimal adjustments, broadening the scope of potential targets. Its use makes malware more challenging to analyze due to the obfuscation capabilities inherent in how Flutter compiles its applications. Its unique structure, particularly the use of the Dart programming language compiled into dynamic library (dylib) files, makes the code inherently obscure, providing a natural avenue for obfuscation. In standard Flutter applications, the app logic is encapsulated in a dylib, loaded by the Flutter engine rather than directly by the primary executable. This level of abstraction complicates the analysis process as the dylib is not explicitly referenced in the main application executable. While this architecture is designed to optimize cross-platform compatibility, it inadvertently serves as a highly effective method for concealing malicious logic. ![Flutter Layout](https://sb-cms.s3.ap-south-1.amazonaws.com/flutter_0c0702e574.jpg) ***Flutter Layout (Source: Jamf)*** ### Anatomy of the Discovered Malware The identified malware functions as a stage-one payload, meaning it serves as the initial component in a multi-stage attack designed to establish a foothold, gather information, or prepare the system for more complex payloads that follow. Among the samples, six infected applications were detected, with five bearing valid developer signatures that had already been revoked by Apple at the time of discovery. One such app, titled _"New Updates in Crypto Exchange,"_ presented itself as a functional minesweeper game. However, upon execution, it initiated a network request to a domain (_“mbupdate[.]linkpc[.]net”_) previously linked to DPRK malware campaigns. The malicious code was deeply embedded within the application, with pre-compiled Dart snapshots complicating any decompilation or analysis attempts due to the need for specialized tools and the extra layer of abstraction that Dart introduces. Further investigation revealed that the malware could execute remote AppleScript commands, such as launching applications, modifying system settings, or downloading additional malicious components. This capability allows attackers to take control of infected devices using sophisticated payload delivery mechanisms. ### Golang and Python Variants In addition to the Flutter version, Jamf Threat Labs also [identified](https://www.jamf.com/blog/jamf-threat-labs-apt-actors-embed-malware-within-macos-flutter-applications/) Go and Python variants of the malware. The [Golang](https://www.secureblink.com/cyber-security-news/chinese-hackers-dragon-spark-use-golang-to-launch-espionage-attacks) variant, similarly signed and notarized by Apple, mirrored the network request and payload execution seen in the Flutter version. This included making HTTPS requests to command-and-control servers and executing payloads, using comparable obfuscation and scripting techniques. The use of different programming languages, such as Golang and Flutter, highlights the attackers' adaptability and their ability to exploit various ecosystems, which complicates detection and mitigation by requiring different analysis tools and expertise for each language. This further demonstrated the attackers' adeptness at exploiting different programming ecosystems to maintain their campaign's adaptability. ![https://www.bleepstatic.com/images/news/u/1220909/2024/Phishing/24/signed.jpg](https://sb-cms.s3.ap-south-1.amazonaws.com/signed_6f8ba5bc61.jpg) ***Trojanized Mindsweeper (Source: Jamf)*** The Python variant, built using Py2App, was crafted as a standalone application. While it appeared to be a functional notepad app, malicious components were embedded within the Python script, enabling it to send and execute commands from a remote server. The consistent use of 'osascript' across these variants suggests a preference for exploiting native macOS features to achieve execution. Leveraging native features like 'osascript' allows attackers to exploit macOS's trusted components, such as built-in automation tools like Automator, making the malware more difficult to detect and resist. By leveraging its trusted status within macOS environments, attackers make detection even more challenging. For instance, 'osascript' has been previously used in malware attacks to execute AppleScript commands, which are often trusted by the system and less likely to trigger traditional antivirus alerts, making this technique particularly effective in avoiding detection. ### A New Testing Ground for Future Attacks? The findings suggest that this malware campaign could be a test run for future, more extensive attacks. The use of legitimate-looking applications, such as those with similar names to popular software or polished user interfaces, along with signed developer accounts and advanced obfuscation techniques, suggests a deliberate effort to bypass security measures. This points towards a strategic probing of macOS's security architecture, indicating attackers' intent to identify and exploit weaknesses in the system. DPRK's history of leveraging sophisticated social engineering campaigns further raises concerns about the potential evolution of these malware tools. The clear mismatch between the content of these apps and their filenames—where the app names suggest legitimate functionality, but the actual code contains malicious behavior—implies an attempt to test whether Apple’s notarization process could be circumvented with carefully concealed malicious components. Additionally, the use of Flutter as a delivery mechanism is a novel approach for DPRK actors, demonstrating their willingness to experiment with different frameworks and methodologies to evade security measures. ### Conclusion and Implications for macOS Security The discovery of DPRK-backed malware utilizing Flutter-built applications to target macOS users highlights the evolving threat landscape. This sophisticated campaign illustrates how attackers refine their tactics to exploit legitimate development frameworks and leverage vulnerabilities in Apple's notarization process. Although it remains uncertain whether this specific malware campaign was intended for broad deployment or as a proof of concept, it underscores the need for heightened vigilance and more robust security defenses for macOS. To counter these threats effectively, measures could include stricter application signing requirements, enhancing behavioral detection systems using machine learning-based anomaly detection tools (e.g., CrowdStrike Falcon, Microsoft Defender for Endpoint), and employing advanced threat-hunting tools like Splunk or Carbon Black to identify unusual patterns and vulnerabilities. Jamf Threat Labs remains committed to monitoring and analyzing further developments in this campaign, ensuring that macOS users are well-protected against emerging threats. ### Indicators of Compromise (IOCs) The following domains, signatures, and application identifiers have been flagged as part of this investigation: - Domain: mbupdate[.]linkpc[.]net - Applications: "New Updates in Crypto Exchange (2024-08-28).app" - Malware signatures: Flutter dylib containing Dart snapshots (_kDartVmSnapshotData, _kDartIsolateSnapshotInstructions) For detailed technical insights and mitigations, Jamf Threat Labs has your back—while Jamf solutions ensure macOS security for everything else.

loading..   13-Nov-2024
loading..   7 min read
loading..

Ransomhub

Halliburton faces a $35 million loss after a ransomware attack, with ongoing ris...

The consequences of the August ransomware attack on [Halliburton](https://www.secureblink.com/cyber-security-news/halliburton-s-global-business-operations-crippled-by-major-cyberattack) are becoming increasingly clear, exposing vulnerabilities in the company's security systems, such as outdated firewalls and poor network segmentation. As the company continues to mitigate the aftermath, experts point out that the underlying risks extend beyond the immediate $35 million loss that initially grabbed headlines. These risks include potential reputational damage, loss of customer trust, increased regulatory scrutiny, and the possibility of further cyberattacks. ### **mmediate Response and Lingering Concerns** Halliburton, a global giant in the energy services sector, suffering significant disruption following the [August breach](https://www.secureblink.com/cyber-security-news/210-victims-in-halliburton-cyberattack-linked-to-ransom-hub-ransomware) by the RansomHub ransomware gang. The company’s swift response—shutting down IT systems and disconnecting customer platforms—helped contain the immediate impact. However, it only addressed the short-term disruption. A larger issue remains regarding the long-term implications of the stolen data, such as legal consequences, reputational damage, operational changes, and potential misuse. The focus now is on the nature of the data stolen—including employee records, client contracts, proprietary operational data, and sensitive financial details—and the potential long-term consequences for Halliburton and its clients. In its August 23 filing with the U.S. Securities and Exchange Commission (SEC), Halliburton disclosed that the breach involved unauthorized access to its internal systems. Later, a subsequent 8-K Form confirmed that threat actors had successfully exfiltrated sensitive information from the company’s network. However, the specifics of what data was stolen remain unclear, with ongoing investigations keeping stakeholders in the dark. ### **Potential Consequences and Legal Risks** This lack of clarity has raised concerns about the potential exposure of highly confidential client information, which could lead to cascading consequences—including regulatory penalties, loss of major clients, legal actions, and a severe blow to Halliburton’s brand reputation. Industry experts are increasingly cautious, emphasizing that should sensitive data be sold or leaked, Halliburton could face numerous lawsuits and regulatory challenges. These challenges include potential fines from data privacy regulators and compliance issues under industry-specific cybersecurity mandates, especially if client-specific proprietary information or trade secrets were compromised. ### **Halliburton Earnings and Strategic Measures** The recent update from Halliburton’s earnings report suggests that while the company experienced a minor financial hit in the short term—a $0.02 per share impact—the broader implications of data leakage are likely far from over. Chairman and CEO Jeff Miller has expressed optimism, asserting that the company’s overall financial targets remain intact, with free cash flow and shareholder returns expected to improve in the upcoming quarter. He emphasized that the company is focusing on strategic cost-cutting measures, strengthening client relationships, and investing in enhanced cybersecurity defenses to achieve these targets amidst ongoing challenges. However, this optimism contrasts sharply with the ongoing uncertainty regarding the stolen data. The company faces dual challenges: maintaining financial stability and addressing unresolved cybersecurity threats, such as potential backdoors left by attackers, incomplete remediation efforts, and the risk of future data leaks. It is increasingly evident that the cyberattack's legacy will extend beyond immediate operational disruptions and short-term financial losses. ### **Long-Term Impacts and Stakeholder Trust** A critical nuance in this situation is the uncertainty regarding the scope of data held by the ransomware group. Unlike direct financial losses, data-related breaches often have a staggered impact, manifesting over months or even years as stolen information can be repurposed or resurfaced in ways that damage both clients and companies alike. For example, the Equifax data breach of 2017 led to long-term impacts including identity theft and substantial legal and regulatory repercussions, illustrating how such incidents can have extended consequences. Data stolen today might be used in future phishing attacks or sold to competitors, leading to identity theft or industrial espionage. Such actions create ongoing and far-reaching risks. Experts have highlighted that even the simple act of maintaining trust among Halliburton’s stakeholders—whether they are investors, partners, or clients—requires careful and deliberate effort following such a breach. Investors may expect clear, consistent updates on cybersecurity improvements, partners might be concerned about data-sharing security, and clients could fear future breaches affecting their own sensitive information. Specific actions, such as enhanced communication with clients, increased transparency about security measures, and offering identity protection services, could be crucial in rebuilding this trust. The attack also puts a spotlight on the systemic vulnerabilities faced by large corporations dependent on interconnected IT infrastructure. As Halliburton scrambles to bolster its cybersecurity posture, it becomes evident that companies across the energy sector must reevaluate their digital defenses by conducting regular penetration tests, increasing employee cybersecurity training, and enhancing incident response plans. Cybersecurity specialists argue that the breach underscores the importance of implementing robust zero-trust architecture, which requires strict verification for every user or device attempting to access resources. Additionally, frequent security audits are crucial, rather than relying solely on reactive measures post-incident. These proactive steps could help mitigate the risks of similar breaches in the future. ### **Halliburton's Recovery Plan and Industry Insights** For Halliburton, the narrative from here is not just about financial recuperation but about proactively addressing concerns related to the stolen data. While immediate [revenue projections](https://ir.halliburton.com/static-files/bd0b8a6f-bf31-434e-bc9d-2ee0532e89d2) seem stable, the potential long-term costs associated with data misuse could dwarf the initially reported $35 million hit. The trajectory of these events will likely shape the company's strategy in navigating cybersecurity resilience, legal liabilities, and reputation management over the coming months. ### **Key Takeaways for Preventing Ransomware Attacks** As the investigation progresses, the industry at large is keeping a close watch. Halliburton’s experience serves as a stark reminder—ransomware breaches do not just affect the present; their legacy can linger, threatening future stability through potential regulatory fines, ongoing litigation, and long-term reputational damage if critical data remains at risk. To mitigate these risks, companies should implement stronger cybersecurity protocols, regularly update their security measures, and conduct thorough training for employees to recognize and respond to cyber threats.

loading..   12-Nov-2024
loading..   6 min read
loading..

AWS

PyPl

Fabric

Fabrice malware, a PyPI typosquatting supply chain attack, steals AWS credential...

A malicious Python package named `fabrice` has infiltrated the Python Package Index (PyPI) since 2021. It targets developers by impersonating the legitimate 'fabric' library—a widely-used tool for SSH automation. This type of attack, known as typosquatting, tricks users into installing a harmful package with a similar name. This attack exploits the trust developers place in commonly used libraries, allowing attackers to easily infiltrate projects with minimal effort. Typosquatting is a particularly effective technique because it relies on human error—developers might mistype the name of a package or fail to notice a subtle difference in spelling. By mimicking the legitimate package name, attackers create a situation where unsuspecting users unknowingly introduce malicious software into their environments. The 'fabrice' package was downloaded over 37,000 times, indicating how successful such attacks can be. ### Platform-Specific Malicious Actions Once installed, 'fabrice' carries out platform-specific malicious actions on both Linux and Windows systems, primarily aimed at stealing credentials and maintaining long-term access. The malware behaves differently depending on the host operating system, tailoring its actions to maximize impact and avoid detection. #### Malicious Actions on Linux On Linux, `fabrice` creates hidden directories and downloads obfuscated payloads (payloads that are intentionally made difficult to understand in order to hide malicious actions), ensuring persistence while evading detection. Specifically, it sets up hidden directories in the user's home directory, such as `~/.local/bin/vscode`, to store malicious files. These files are downloaded from an external server controlled by the attacker, making it difficult for traditional security [tools](http://github.com/apps/socket-security) to detect [them](https://socket.dev/blog/malicious-python-package-typosquats-fabric-ssh-library). The obfuscated payloads are designed to execute commands with the same privileges as the user, allowing the attacker to establish a foothold in the system. By using obfuscation techniques, the malware makes it challenging for security analysts to analyze its true intent. These hidden directories are rarely inspected by users, which helps the malware maintain a low profile and persist on the system for extended periods. #### Malicious Actions on Windows On Windows, `fabrice` takes a slightly different approach. It downloads an encoded payload (in base64 format) that contains a VBScript (`p.vbs`). This VBScript is responsible for launching another hidden Python script (`d.py`). The use of VBScript helps maintain stealth, as it allows the malware to execute Python code without opening a visible command prompt window. The Python script (`d.py`) downloads a malicious executable (`chrome.exe`), which is stored in the user's Downloads folder. The executable's purpose is to establish persistence by creating a scheduled task that runs every 15 minutes. This ensures that even if the system reboots, the malware will continue to execute and maintain control. By using legitimate Windows features like scheduled tasks, 'fabrice' blends in with typical system behavior, making it more difficult for traditional antivirus solutions to detect its presence. ### The Risks of Supply Chain Attacks With over 37,000 downloads, largely due to the popularity of the legitimate 'fabric' library, this sophisticated supply chain attack highlights the risks inherent in open-source dependencies. Attackers leverage typosquatting to compromise unsuspecting developers, exfiltrate sensitive credentials, and establish backdoors for long-term system access. Open-source software is a cornerstone of modern development, offering flexibility, cost savings, and community-driven innovation. However, it also presents a significant risk when malicious actors exploit the open nature of these ecosystems. By targeting widely used packages like 'fabric', attackers can infiltrate numerous projects and organizations with a single malicious package. This highlights the importance of verifying package authenticity before installation. The consequences of such supply chain attacks are severe. In the case of 'fabrice', the primary objective is to steal AWS credentials. These credentials are invaluable to attackers, as they can provide access to sensitive cloud resources, allowing them to exfiltrate data, run costly operations, or even take control of cloud infrastructure. The use of the official Python SDK (`boto3`) to access AWS credentials means that any system running 'fabrice' could inadvertently leak cloud access keys, leading to substantial security breaches and financial losses. The success of 'fabrice' also points to the need for enhanced monitoring and proactive defense mechanisms in the software development lifecycle. Developers and organizations must adopt best practices, such as using package management tools that verify the integrity of software components, implementing multi-factor authentication for cloud accounts, and conducting regular security audits of dependencies. ### Mitigation Strategies Mitigating the risk of typosquatting and supply chain attacks requires a combination of vigilance and proactive measures. Here are some strategies that developers and organizations can adopt to protect themselves from similar threats: 1. **Verify Package Authenticity**: Always verify the source and authenticity of packages before installing them. Tools like `pip` offer features to check the package signatures, and developers should take advantage of these features. 2. **Use Trusted Repositories**: Stick to well-known and trusted repositories. When possible, use verified versions of packages or direct links from official project pages to minimize the risk of installing compromised packages. 3. **Enable Multi-Factor Authentication (MFA)**: Protect your cloud accounts, such as AWS, with MFA. This additional layer of security can prevent unauthorized access, even if credentials are compromised. 4. **Monitor Dependencies**: Use automated tools to monitor dependencies for vulnerabilities. Tools like Dependabot or Snyk can help keep track of outdated or potentially malicious dependencies and recommend updates or patches. 5. **Conduct Regular Audits**: Perform regular audits of all dependencies in your projects. This involves checking the list of installed packages, ensuring they are from reputable sources, and removing any that are unnecessary or untrusted. 6. **Use Runtime Application Self-Protection (RASP)**: Implementing RASP solutions can help detect and block malicious behavior during runtime, providing an additional layer of security beyond static code analysis. The popularity of open-source libraries like `fabric` makes them an attractive target for cybercriminals. With over 37,000 downloads, `fabrice` demonstrates how quickly malicious packages can spread within the developer community. Developers and organizations must remain vigilant, adopt best practices for dependency management, and take proactive steps to secure their software supply chains. To learn more about how to secure your systems and protect against similar attacks, discover the comprehensive analysis of the **Fabrice Malware Threat Research** [here](https://www.secureblink.com/threat-research/fabrice-malware-python-typosquatting-targeting-aws-via-supply-chain-on-linux-and-windows-1).

loading..   11-Nov-2024
loading..   6 min read