As reported by BleepingComputer, Ukraine's Computer Emergency Response Team (CERT-UA) has identified an active attack campaign distributing trojanized archives that bundle the legitimate Notepad++ text editor with a malicious plugin-disguised utility called LunchPoke. This campaign is a textbook example of how adversaries weaponize trusted, widely-used developer tools to slip past both technical controls and user suspicion.

Threat Alert: As reported by BleepingComputer, Ukraine's Computer Emergency Response Team (CERT-UA) has identified an active attack campaign distributing trojanized archives that bundle the legitimate Notepad++ text editor with a malicious plugin-disguised utility called LunchPoke.

Why This Attack Vector Is Particularly Dangerous

Notepad++ enjoys enormous trust across developer, analyst, and IT operations communities. Its plugin architecture — designed to extend functionality — is a feature, not a bug. But that extensibility creates an exploitable attack surface. When a malicious component arrives bundled with a legitimate, signed application, it dramatically reduces the likelihood that endpoint detection tools or vigilant users will flag the installation.

What makes LunchPoke especially concerning is the persistence angle. Unlike malware that relies on a single execution vector, persistence mechanisms ensure that even after reboots, credential rotations, or partial remediation efforts, the attacker maintains a foothold. This transforms an initial compromise into a long-term intrusion — exactly the kind of quiet, durable access that precedes data exfiltration, lateral movement, or ransomware staging.

Shield53 Perspective: Plugin-based persistence in trusted applications represents a growing blind spot for enterprise defenders. Many organizations whitelist well-known applications wholesale — including their associated file paths and plugin directories — without monitoring for anomalous plugin additions.

Who Is Most at Risk

Why This Attack Vector Is Particularly Dangerous
Software developers and DevOps teams who routinely use Notepad++ and may download plugins or bundled utilities from unofficial sources
Ukrainian government and critical infrastructure entities, given CERT-UA's involvement and the geopolitical context
IT administrators in environments where Notepad++ is a standard tool and plugin directories are not monitored
Organizations with permissive application whitelisting policies that trust entire application directories rather than specific executables

The Broader Supply Chain and Trojanization Trend

This campaign fits a well-established and escalating pattern: adversaries identifying high-trust, low-scrutiny software and repurposing it as a delivery mechanism. We've seen similar techniques used with 3CX, SolarWinds, and various open-source developer tools. The common thread is that defenders tend to extend implicit trust to widely recognized software — and attackers know it.

The archive delivery mechanism is also notable. Distributing a bundled archive (rather than a standalone malicious file) can circumvent file-based reputation systems that evaluate executables in isolation. When Notepad++ itself is clean and signed, security tools may not scrutinize the accompanying files as aggressively.

Detection Considerations

Defenders should focus detection efforts on several behavioral indicators rather than relying solely on signature-based controls:
  • Unexpected files appearing in Notepad++ plugin directories (typically %ProgramFiles%\Notepad++\plugins\ or the user-profile equivalent)
  • Notepad++ or child processes making outbound network connections — particularly to unusual or newly registered domains
  • Registry modifications or scheduled task creation coinciding with Notepad++ execution
  • Archives delivered via phishing or messaging platforms that contain mixed legitimate/malicious content
  • Process creation chains where notepad++.exe spawns unexpected child processes

Shield53 Recommendations

Immediate Actions

  • Audit Notepad++ installations across your environment. Verify plugin directories contain only known, expected plugins — cross-reference against official Notepad++ plugin repositories.
  • Restrict plugin directory write permissions so that standard user accounts cannot add new files to Notepad++ plugin folders without administrative approval.
  • Source software only from official channels — enforce policy requiring that Notepad++ and its plugins be downloaded exclusively from notepad-plus-plus.org or verified enterprise repositories.
  • Enable application control logging to capture execution events from plugin directories, and alert on any new executable or DLL appearing in those paths.
  • Hunt for LunchPoke indicators using CERT-UA's published IOCs — search endpoint telemetry for associated file hashes, registry keys, and network indicators.

Strategic Hardening

  • Implement MITRE ATT&CK T1176 (Browser Extensions) and T1546 (Event Triggered Execution) detection logic — plugin persistence maps closely to these technique families.
  • Evaluate whether Notepad++ plugin functionality is necessary across your user base. For users who don't require plugins, consider deploying a plugin-disabled configuration.
  • Incorporate software composition analysis into your toolchain — not just for code you build, but for packaged tools your teams use daily.

The LunchPoke campaign is a reminder that the attack surface isn't limited to your infrastructure — it extends to every tool your people trust and use every day. Defenders who monitor behavior rather than relying on reputation alone will be best positioned to catch these intrusions early.