LucidRook: Lua-based malware hits Taiwanese NGOs and universities

Cisco Talos details LucidRook, a Lua-scripted backdoor from UAT-10362 spread by phishing to Taiwanese NGOs. Infection chains, IOCs and detection tips.

TechLogHub Engineering Team
April 9, 2026
3 min read
0 views

Share Article

New ‘LucidRook’ malware used in targeted attacks on NGOs, universities

Cisco Talos has documented LucidRook, a new malware family that embeds a full Lua interpreter and pulls its real behaviour down as Lua bytecode. A group Talos tracks as UAT-10362 used it in spear-phishing against Taiwanese NGOs and, it suspects, universities. The targets are narrow, but the design is worth understanding. A small, stable loader plus a swappable script payload is an architecture developers will recognise, and it makes life hard for defenders.

What happened

Talos published its research on 8 April 2026. It first saw LucidRook in October 2025, delivered in a spear-phishing email to a Taiwanese NGO. Executable variants then appeared on public malware repositories in December 2025. Talos assesses with medium confidence that this is a targeted intrusion campaign.

It describes two infection chains, both starting from password-protected archives:

  • LNK chain: A shortcut disguised with a PDF icon launches a legitimate Pester PowerShell script (a living-off-the-land technique). The script runs a DISM-related binary, which sideloads the LucidPawn dropper as DismCore.dll. LucidPawn copies the DISM binary into %APPDATA% renamed as msedge.exe, drops the LucidRook stager as a new DismCore.dll, adds Startup-folder persistence and opens a decoy document styled as a Taiwanese government letter.
  • EXE chain: A Cleanup.exe posing as Trend Micro Worry-Free Business Security Services drops its payloads into C:\ProgramData, adds persistence and shows a fake "cleanup completed" message.

LucidPawn runs only if the Windows UI language is Traditional Chinese (zh-TW or zh-HK), so it exits early on English-language sandboxes.

Who is affected

  • Taiwanese NGOs and suspected universities, the targets Talos observed.
  • Windows users who open password-protected archives from email. Those archives get past many gateway scanners.
  • Two Taiwanese printing companies, whose FTP servers (1.34.253[.]131 and 59.124.71[.]242) were abused using credentials the companies had published on their own websites.

What it means for developers and engineering teams

The LucidRook stager is a roughly 1.6 MB 64-bit DLL with more than 3,800 functions. It embeds Lua 5.4.8 plus Rust-compiled libraries. It checks for Lua bytecode magic, runs in a custom "safe mode" that disables package.loadlib, and obfuscates its strings with per-string XOR keys. It collects host reconnaissance data, RSA-encrypts it, puts it in a password-protected ZIP and uploads it over plaintext FTP. It then fetches archive1.zip and runs the Lua bytecode inside. Because operators can host that payload only briefly, Talos never captured a decryptable second stage. That is the point: if responders recover only the loader, they learn almost nothing about what the attackers did.

A companion tool, LucidKnight, profiles hosts and sends its results by email through Gmail SMTP using the Rust lettre crate. Two lessons for engineers:

  • Embedded scripting engines (Lua, JavaScript, Python) are now standard malware architecture, just as in game engines and plugin systems. Code you can't see at rest is code you can't review.
  • Any credential you publish, even for a "public upload" FTP, becomes attacker infrastructure. The same goes for open S3 buckets, public webhooks and shared tokens in documentation.

What to do now

  1. Block or quarantine password-protected archives from external senders, or route them to a sandbox that can prompt for the password.
  2. Alert on DLL sideloading from user-writable paths, such as signed binaries like msedge.exe running from %APPDATA% or C:\ProgramData instead of Program Files.
  3. Watch for LNK files that launch PowerShell or LOLBAS scripts like Pester, and for new entries in the Startup folder.
  4. Flag outbound plaintext FTP and unexpected SMTP to Gmail from endpoints that shouldn't send mail.
  5. Deploy Talos detections: ClamAV Win.Backdoor.LucidRook-10059729-0 and related signatures, Snort 2 SIDs 66108 to 66111 and Snort 3 SIDs 301447 and 301448. Load the IOCs from Talos' GitHub.
  6. Audit your own public-facing credentials. Never publish shared upload credentials. Use per-user, scoped, expiring upload links.

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.

LucidRook Lua Malware Targets Taiwan NGOs (UAT-10362) | New Lucidrook Malware Used In Targeted Attacks On Ngos Universities