Notepad++ Update Mechanism Hijacked in 6-Month Supply Chain Attack by Chinese APT

Chinese State-Sponsored Group Lotus Blossom Compromises Notepad++ Update Infrastructure

HIGH
February 3, 2026
7m read
Supply Chain AttackThreat ActorMalware

Related Entities

Threat Actors

Organizations

Products & Tech

Other

Full Report

Executive Summary

On February 2, 2026, the developers of Notepad++ revealed that its update infrastructure was compromised in a sophisticated supply chain attack lasting from June to December 2025. Security researchers attribute the operation with high confidence to Lotus Blossom (also known as Billbug), a Chinese state-sponsored threat actor. The attackers compromised a shared hosting server, allowing them to intercept and redirect update requests from the Notepad++ client. This enabled the selective delivery of malicious payloads to a small, targeted set of victims, primarily for espionage purposes. The campaign utilized a previously undocumented backdoor called 'Chrysalis' and leveraged complex execution chains involving legitimate but vulnerable software to deploy payloads like Cobalt Strike.


Threat Overview

The attack did not compromise the Notepad++ source code but instead targeted the distribution mechanism. By gaining control of the hosting server, Lotus Blossom could manipulate the update process. When a targeted user's Notepad++ instance checked for updates via the GUP.exe utility, the request was redirected to an attacker-controlled server. This server then delivered a malicious update.exe file instead of the legitimate update. The campaign was highly targeted, with victims identified in the Philippines, Vietnam, El Salvador, and Australia. Affected organizations included a government entity and a financial institution, underscoring the espionage focus of the operation. The breach was first detected and stopped on December 2, 2025, but the attackers demonstrated persistence by retaining access to some internal services even after their initial server access was revoked in September 2025.

Technical Analysis

The attack chain showcases the actor's sophistication and ability to adapt. Forensic analysis by Rapid7 indicates that the legitimate execution of notepad++.exe and GUP.exe was followed by the execution of the malicious update.exe downloaded from an attacker-controlled IP address. This led to the deployment of the 'Chrysalis' backdoor.

Researchers at Kaspersky observed multiple, distinct execution chains, indicating the attackers rotated their TTPs to evade detection:

  1. Chain 1 (NSIS Installer): A malicious NSIS installer was used to drop a vulnerable version of the legitimate 'ProShow' software. A DLL side-loading technique was then used against this vulnerable software to trigger an exploit, which in turn decrypted and executed a Metasploit downloader. The final payload was a Cobalt Strike Beacon.
  2. Chain 2 (Lua Script): Another observed chain utilized a malicious Lua script to achieve a similar outcome, demonstrating the use of varied toolsets.

MITRE ATT&CK Techniques

Impact Assessment

The primary impact of this campaign was espionage against targeted government and financial organizations. For the affected entities, the breach could lead to the loss of sensitive state or commercial secrets, intellectual property, and internal financial data. Although the number of victims was small, the impact on them is severe. For the wider user base of Notepad++, the incident erodes trust in the software's update mechanism and highlights the significant risks associated with software supply chains, even for popular open-source projects. Organizations that use Notepad++ must now consider the possibility of compromise and perform forensic analysis if they match the victim profile.

Cyber Observables for Detection

Type Value Description
Process Name update.exe Suspicious update process executed from a temporary or user-writable directory, not the standard Notepad++ program folder.
Network Traffic Pattern Outbound connections from GUP.exe or notepad++.exe to non-official Notepad++ domains. Monitor for connections to unusual IP addresses or domains during the update check process.
File Path %TEMP%\update.exe A common location for downloaded malicious updaters.
Process Chain GUP.exe -> cmd.exe -> update.exe Unusual process creation chain originating from the Notepad++ updater.

Detection & Response

Security teams should proactively hunt for signs of this activity.

  1. Log Analysis: Review proxy, DNS, and firewall logs for connections from endpoints running notepad++.exe or GUP.exe to suspicious or known malicious IP addresses between June and December 2025. Correlate this with process execution logs (e.g., Windows Event ID 4688) on those endpoints.
  2. EDR Queries: Use Endpoint Detection and Response (EDR) solutions to search for historical process execution chains where GUP.exe spawns unexpected child processes like cmd.exe or powershell.exe, or writes an update.exe file to a temporary directory.
  3. File System Search: Scan for vulnerable versions of ProShow software in unexpected locations, as this was used as part of an execution chain.
  4. D3FEND Techniques: Implement D3-NTA - Network Traffic Analysis to baseline normal update traffic and detect anomalies. Use D3-FA - File Analysis to inspect downloaded update packages for malicious characteristics before execution.

Mitigation

This attack highlights the importance of defense-in-depth, as compromising a single server led to a significant breach.

Immediate Actions:

  • Organizations fitting the target profile (government/finance in Southeast Asia) that use Notepad++ should immediately initiate a forensic investigation.
  • Manually update Notepad++ from the official website after verifying the download's integrity. Disable the automatic update feature temporarily.

Strategic Recommendations:

  1. Application Control: Implement application control solutions, such as Windows Defender Application Control (WDAC), to restrict the execution of unauthorized binaries. This could prevent the malicious update.exe from running. This relates to D3FEND's D3-EAL - Executable Allowlisting.
  2. Network Egress Filtering: Restrict outbound traffic from endpoints to only known-good domains and IP addresses. This can block C2 communications and the download of additional payloads. This is a form of D3FEND's D3-OTF - Outbound Traffic Filtering.
  3. Software Bill of Materials (SBOM): For developers and large enterprises, maintaining an SBOM helps track all components and dependencies, enabling faster response when a component like Notepad++ is implicated in an attack.
  4. User Training: While this attack was sophisticated, reinforcing user awareness about unexpected update prompts remains a valuable layer of defense.

Timeline of Events

1
June 1, 2025
The supply chain attack on Notepad++ infrastructure begins.
2
September 1, 2025
Attackers lose initial server access but maintain persistence on some internal services.
3
December 2, 2025
The breach is detected and terminated by Notepad++ maintainers.
4
February 2, 2026
Notepad++ and security firms publicly disclose the supply chain attack.
5
February 3, 2026
This article was published

MITRE ATT&CK Mitigations

Use application control policies to prevent the execution of unauthorized updaters like the malicious 'update.exe'.

Mapped D3FEND Techniques:

Implement strict egress filtering to block outbound connections to unknown C2 servers, preventing payload delivery and data exfiltration.

Audit

M1047enterprise

Enable detailed process and network logging to detect anomalous behavior from legitimate applications like GUP.exe.

Mapped D3FEND Techniques:

While the code itself wasn't compromised, enforcing that all executables must be signed by trusted publishers can help mitigate the execution of unsigned malicious files.

D3FEND Defensive Countermeasures

Implement Network Traffic Analysis (NTA) solutions to monitor outbound connections from all endpoints, with a specific focus on traffic originating from software update utilities like Notepad++'s GUP.exe. Establish a baseline of normal update behavior, including destination domains (e.g., notepad-plus-plus.org) and typical data volumes. Configure alerts for any deviation from this baseline, such as connections to newly observed domains, IP addresses with poor reputation, or traffic patterns indicative of C2 communication. This technique is critical for detecting the initial redirection of the update request, which was the pivotal point in this supply chain attack. By flagging the anomalous connection before the malicious payload is downloaded, security teams can intervene early in the kill chain.

Deploy a robust application allowlisting policy, such as Windows Defender Application Control (WDAC), across all endpoints, especially servers and workstations handling sensitive data. In the context of this attack, a properly configured allowlisting rule would have prevented the malicious update.exe from executing, as it would be an unsigned or improperly signed binary originating from an untrusted location (e.g., a temporary user folder). The policy should enforce that only digitally signed executables from trusted publishers are allowed to run. This moves beyond simple hash-based allowlisting and provides a resilient defense against attackers dropping novel malicious files onto a system, effectively breaking the execution chain after the malicious download.

Sources & References

Notepad++ Updates Hijacked By Suspected Chinese Hackers - Grand Pinnacle Tribune
Grand Pinnacle Tribune (grandpinnacletribune.com) February 2, 2026
The Notepad++ supply chain attack – unnoticed execution chains and new IoCs
Kaspersky Securelist (securelist.com) February 3, 2026
Notepad++ supply chain attack: Researchers reveal details, IoCs, targets
Help Net Security (helpnetsecurity.com) February 3, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

supply chainespionageAPTbackdoorcode signingopen source

📢 Share This Article

Help others stay informed about cybersecurity threats

Continue Reading