LabubaRAT: Rust-based RAT Disguised as NVIDIA Container Runtime Toolkit

LabubaRAT: Rust-based RAT Disguised as NVIDIA Container (TL-2026-1401), also tracked as LabubaRAT, is a high-severity malware campaign, first published 2026-07-15. It has no confirmed attribution, affects Microsoft Windows (desktop, all currently supported versions), maps to 17 MITRE ATT&CK techniques (T1005, T1033, T1036), and is covered by 9 detection rules and 22 indicators of compromise.

Key facts for TL-2026-1401

Threat ID
TL-2026-1401
Also known as
LabubaRAT
Severity
HIGH
Status
ACTIVE
Category
MALWARE
First published
2026-07-15
Last reviewed
2026-07-15
Attribution confidence
LOW
Motivation
FINANCIAL
Detection rules
9
Indicators of compromise
22

Malware and tooling in LabubaRAT: Rust-based RAT Disguised as NVIDIA Container

Malware and tooling: LabubaRAT, LabubaPanel, LabubaRAT MaaS platform

LabubaRAT is a newly documented Rust-based remote access trojan, identified by Blackpoint Cyber's Adversary Pursuit Group (APG), that masquerades as an unsigned NVIDIA Container Runtime component (nvidia-sysruntime.exe). It provides command execution, PowerShell/JavaScript execution, screenshot capture, file transfer, SOCKS5 proxying, and HKCU Run-key persistence, communicating via HTTPS polling, Microsoft Edge WebView2, and DNS tunneling, with runtime-configurable, malware-as-a-service style deployment infrastructure.

How LabubaRAT: Rust-based RAT Disguised as NVIDIA Container works

LabubaRAT is a Rust-compiled (reqwest/hyper/rustls/tokio) remote access trojan first surfaced publicly on 2026-07-15 via Blackpoint Cyber's Adversary Pursuit Group (APG) research, and subsequently corroborated by Help Net Security, The Hacker News, GBHackers, and CyberSecurityNews. The observed sample, nvidia-sysruntime.exe, is an unsigned 64-bit Windows GUI executable that impersonates NVIDIA's Container Runtime Toolkit through version metadata, a PDB path (nvidia_container.pdb), a single-instance mutex (Local\NVIDIAContainerMonitor_SingleInstance), and a local SQLite database (nvctr_sys.db) styled to look like a legitimate NVIDIA component. The build carries a compile timestamp of 2026-06-17 23:16:55 UTC and a Rust cargo build path referencing the developer username "funt".

Unlike malware with hardcoded C2 infrastructure, LabubaRAT is configured at deployment time via command-line arguments (--org, --key, --group, --server, --b, --install, --uninstall) or ZM_-prefixed environment variables, allowing the same compiled binary to be reused across multiple campaigns and operators without recompilation — a strong malware-as-a-service (MaaS) indicator. A Base64-encoded --b parameter packs organization, group, server, and API-key values together; APG decoded one observed deployment to reveal organization "luxespa", group "rabbit", and C2 server pipicka[.]xyz, with associated infrastructure IPs 191.44.109[.]130, 87.120.108[.]18, and 168.222.254[.]204. The C2 infrastructure exposes a panel APG dubbed "LabubaPanel" based on its page title and a Labubu-themed favicon; other observed deployment group tags include room-1, sauna, and vip-chair, consistent with a shared criminal platform serving multiple tenants.

Operationally, LabubaRAT registers the infected host, then accepts operator tasking to execute shell commands (cmd), PowerShell, and JavaScript (via wscript.exe, using a wupd_ execution prefix), capture screenshots, upload/download/delete files, create directories, and archive/unarchive data. It relays traffic through a SOCKS5 proxy and communicates over three independent channels — HTTPS polling, Microsoft Edge WebView2, and DNS tunneling — so an operator can retain access even if one channel is blocked or detected. For persistence it writes a Run-key entry under HKCU\Software\Microsoft\Windows\CurrentVersion\Run, providing user-level (non-elevated) autostart. Before tasking, it profiles the host: enumerating installed browsers (Chrome, Firefox, Edge, Brave) and installed security products (Microsoft Defender, CrowdStrike, SentinelOne, Carbon Black, Sophos, Malwarebytes, Bitdefender, ESET, Kaspersky, McAfee, Symantec, Trend Micro) via Windows registry uninstall keys, and collects hostname, CPU/memory specs, domain membership, and UAC elevation state — reconnaissance clearly aimed at gauging EDR/AV coverage and lateral-movement viability before further operator action.

No CVE applies; this is a malware/implant threat rather than a software vulnerability. No attribution to a named threat actor or nation-state has been published; the naming conventions (luxespa, rabbit, room-1, sauna, vip-chair) and configurable multi-tenant architecture point to a criminal MaaS offering rather than a single dedicated operator.

MITRE ATT&CK techniques used in TL-2026-1401

Collection

T1005 Data from Local System; T1113 Screen Capture; T1560 Archive Collected Data

Discovery

T1033 System Owner/User Discovery; T1069 Permission Groups Discovery; T1082 System Information Discovery; T1482 Domain Trust Discovery

Defense Evasion

T1036 Masquerading

Exfiltration

T1041 Exfiltration Over C2 Channel

Execution

T1059 Command and Scripting Interpreter

Command and Control

T1071 Application Layer Protocol; T1090 Proxy; T1102 Web Service; T1572 Protocol Tunneling

execution

T1204 User Execution

discovery

T1518 Software Discovery

Persistence

T1547 Boot or Logon Autostart Execution

Affected products and versions in LabubaRAT: Rust-based RAT Disguised as NVIDIA Container

  • Microsoft — Windows (desktop, all currently supported versions)
    Vulnerable versions: N/A - malware targets Windows generally, not a specific OS version vulnerability
  • NVIDIA — Container Runtime Toolkit (impersonated brand only — NVIDIA software itself is not vulnerable; its name/branding is spoofed by the malicious binary)

Remediation for LabubaRAT: Rust-based RAT Disguised as NVIDIA Container

Immediate actions

  • Block/monitor the C2 domain pipicka[.]xyz and associated infrastructure IPs 191.44.109[.]130, 87.120.108[.]18, 168.222.254[.]204 at perimeter and DNS resolvers
  • Hunt for the mutex Local\NVIDIAContainerMonitor_SingleInstance and the file nvctr_sys.db across endpoints
  • Hunt for unsigned nvidia-sysruntime.exe and any process matching hash SHA256 b7443b0ab48d2f5786d1b6f3a580f02621e9ae5a3877ee3a44e01df13d984328
  • Audit HKCU\Software\Microsoft\Windows\CurrentVersion\Run for unrecognized entries pointing to unsigned NVIDIA-named binaries
  • Alert on wscript.exe spawned by processes named nvidia-sysruntime.exe or similar, and on outbound DNS-tunneling patterns

Workarounds

  • Block execution of unsigned executables named nvidia-sysruntime.exe or referencing nvidia_container.pdb via application control policy

Longer-term hardening

  • Enforce application allowlisting/code-signing verification for binaries claiming NVIDIA/vendor branding, especially in Program Files locations lacking a valid NVIDIA signature
  • Deploy EDR with behavioral detection for HKCU Run-key persistence combined with SOCKS5 proxy and multi-channel (HTTPS/WebView2/DNS) beaconing
  • Restrict or monitor Microsoft Edge WebView2 runtime usage by non-browser processes
  • Educate users/IT on verifying NVIDIA driver/runtime downloads only from nvidia.com or signed vendor channels

Timeline of LabubaRAT: Rust-based RAT Disguised as NVIDIA Container

  • LabubaRAT C2 infrastructure (pipicka[.]xyz and associated IPs 191.44.109.130, 87.120.108.18, 168.222.254.204, hosted on German providers) begins operating, per Blackpoint Cyber APG's assessment that infrastructure came online 'beginning in early June' ahead of the observed sample's compile date
  • Observed nvidia-sysruntime.exe sample compiled (Rust, PE timestamp 2026-06-17 23:16:55 UTC), per Blackpoint Cyber APG analysis
  • Blackpoint Cyber's Adversary Pursuit Group (APG) publishes the original technical analysis identifying and naming LabubaRAT, decoding the Base64 --b configuration parameter to reveal organization 'luxespa', group 'rabbit', and C2 server pipicka[.]xyz
  • TechNadu publishes coverage summarizing LabubaRAT's masquerading technique and Windows persistence mechanism, closing out the initial 24-hour multi-outlet disclosure wave
  • CyberSecurityNews and Cyberpress.org publish independent write-ups confirming the mutex Local\NVIDIAContainerMonitor_SingleInstance, nvctr_sys.db database artifact, and the ZM_-prefixed environment-variable configuration channel
  • GBHackers republishes LabubaRAT technical IOCs, including SHA256 hash b7443b0ab48d2f5786d1b6f3a580f02621e9ae5a3877ee3a44e01df13d984328 and C2 domain pipicka[.]xyz
  • The Hacker News reports on LabubaRAT's multi-channel C2 (HTTPS, WebView2, DNS tunneling) and NVIDIA impersonation
  • Help Net Security publishes coverage of LabubaRAT masquerading as NVIDIA software, syndicating Blackpoint APG's findings

Sources cited for LabubaRAT: Rust-based RAT Disguised as NVIDIA Container

Threats related to LabubaRAT: Rust-based RAT Disguised as NVIDIA Container

Detection coverage for TL-2026-1401

As of 2026-07-15, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1401 across Splunk SPL, Microsoft KQL and Sigma, covering 22 indicator(s) of compromise. The whole corpus is readable without an account; a free account unlocks full detection query text in Splunk SPL, Microsoft KQL and Sigma; paid tiers add raw indicator values, correlation and the MCP server. Threadlinqs MCP server · View plans.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

[ 0 threats ] [ 0 det ] [ CRIT: 0 ] [ HIGH: 0 ]
// threat_feed
$ sort --newest
Showing all threats

Latest Threats