Lazarus Group Exploits Zoho ManageEngine Vulnerability to Target Internet Backbone Infrastructure Provider

The Lazarus Group, a North Korea-linked advanced persistent threat (APT) actor known for its sophisticated cyber attacks, has recently been observed exploiting a vulnerability in Zoho ManageEngine. This exploit led to the compromise of an internet backbone infrastructure provider in Europe. In this article, we will delve into the details of the attack, the timeline, Lazarus Group’s exploitation of the vulnerability, and the implications it holds for organizations around the world.

The attack and timeline

The attack took place in early 2023, just days after proof-of-concept (PoC) exploit code targeting the Zoho ManageEngine flaw was made public. This discovery highlights the inherent risks associated with the release of PoC code. Cybercriminals, like the Lazarus Group, quickly seize the opportunity to leverage such exploits to their advantage, leaving organizations vulnerable to attacks.

Lazarus’ exploitation of CVE-2022-47966

The Lazarus Group utilized the CVE-2022-47966 vulnerability to deploy a new variant of a remote access trojan (RAT) named QuiteRAT. It is essential to note that the successful exploitation of this vulnerability demonstrates the group’s advanced technical capabilities and their ability to adapt their tactics to exploit newly discovered vulnerabilities.

Functionality and Persistence of QuiteRAT

Once executed on a compromised machine, QuiteRAT has the capability to harvest system information, which it then sends to the attackers’ server. Furthermore, QuiteRAT allows the attackers to engage in further system reconnaissance and achieve persistence by modifying the Windows registry. These features grant them prolonged access to the compromised system, enabling them to extract sensitive information and potentially launch further attacks.

Similarities between QuriteRAT and MagicRAT

QuiteRAT, which has been observed in recent Lazarus Group attacks, is notably smaller in size compared to its predecessor, MagicRAT. Additionally, QuiteRAT lacks a built-in persistence mechanism. Both implants employ Base64 encoding to obfuscate their strings and showcase similar functionality aimed at remaining dormant on the endpoint, making detection and analysis more challenging.

Lazarus’ transition to QuiteRAT

Lazarus Group’s decision to replace MagicRAT with QuiteRAT in their recent attacks raises questions about their motives and the strategic shift in their toolset. The move may indicate evolving tactics or an attempt to exploit new vulnerabilities undetected. Understanding this transition is crucial for organizations to anticipate future attacks and take proactive measures to secure their networks.

Lazarus’s targeting of other entities

The attack on the internet backbone infrastructure provider is not an isolated incident. The Lazarus Group has also been targeting healthcare entities in Europe and the US, emphasizing the far-reaching impact and significance of their operations. These attacks highlight the group’s intent to access critical systems and potentially compromise sensitive data, posing a severe threat to the targeted organizations and their stakeholders.

In response to these attacks, Zoho has released patches to address the ManageEngine vulnerability (CVE-2022-47966) for the impacted products. However, this incident serves as a significant reminder of the constant need for vigilance and the importance of promptly implementing security updates and patches. Organizations must remain proactive in assessing their systems’ vulnerabilities, staying informed about emerging threats, and fostering a robust cybersecurity posture to safeguard their networks and sensitive information from the persistent threat posed by groups like Lazarus.

Explore more

Why Is CRM and Trading Platform Integration Essential?

The split-second decisions that define success in the modern forex market leave no room for delayed responses or fragmented data streams that hinder a brokerage’s ability to capitalize on high-value client opportunities. Within the first 48 hours of lead registration, a window of opportunity exists where conversion rates are at their peak. However, many brokerages fail to realize that delayed

What Are the Best Transactional Email Platforms for 2026?

The split-second window between a user’s interaction with a mobile application and the arrival of a confirmation email represents the most critical frontier in the battle for modern consumer confidence. In an era where digital services are judged by their responsiveness, the infrastructure supporting automated communication has evolved from a back-end utility into a primary pillar of the user experience.

Ethereum Sees Record Whale Accumulation Amid Market Rebound

The recent surge in large-scale transactions suggests that institutional players and high-net-worth individuals are aggressively positioning themselves for a sustained upward trend in the decentralized finance ecosystem. While retail investors often react to short-term volatility with caution, the behavior of these massive wallet holders, commonly known as whales, points toward a much deeper level of conviction regarding the underlying value

How Can Leaders Avoid Common Harassment Reporting Mistakes?

The moment a leadership team receives a formal harassment grievance, the organization’s cultural integrity is immediately placed under a high-stakes microscope that reveals the true values of its executive board. Handling these reports requires more than just adherence to legal protocols; it demands a sophisticated understanding of human psychology and a commitment to radical transparency that many traditional corporations still

Can Lightweight Linux Revive Your Obsolete PC?

The silhouette of a dormant laptop gathering dust in a closet is a testament to the rapid cycle of consumer electronics, where perfectly functional hardware is often discarded simply because it can no longer support the weight of modern operating systems. It is estimated that millions of these devices are retired every year, not because of hardware failure, but because