14 Trojanized npm Packages Deliver AI-Assisted Linux Backdoor "RedC2 4.0"

What happened

Researchers at Trend Micro's TrendAI team reported discovering 14 trojanized npm packages disguised as calendar and habit-tracking ("streak") utilities. According to the report, these packages bundle a Linux implant dubbed RedC2 4.0, described as an AI-powered backdoor. Per the reporting, when the malicious module loads it locates the bundled binary, marks it executable, and launches it as a detached background process on the host.

Why it matters for defenders

npm remains a high-trust supply chain that many organizations pull from automatically via CI/CD and developer workstations, often with limited scrutiny of transitive or newly-published packages. A backdoor that specifically targets Linux systems is notable because it can land on build servers, containers, and production infrastructure — not just developer laptops — and a detached background process is designed to persist quietly beyond the lifetime of the install script. The "AI-assisted C2" characterization suggests the operators may be using AI tooling to help drive command-and-control decision-making or evasion, though the underlying report gives limited technical detail on how that manifests.

What defenders should watch for

• Audit npm dependencies (including transitive ones) for calendar/streak-tracker style utility packages installed recently, especially any pulled from public registries outside an internal proxy/allowlist.
• Hunt for postinstall or lifecycle scripts in node_modules that chmod +x a bundled binary and spawn it as a detached/background process.
• Review process trees on Linux build agents, containers, and servers for unexpected child processes originating from Node.js/npm install activity, particularly processes that detach from their parent shell.
• Inspect outbound network connections from CI/CD and application hosts for unusual or newly-observed C2-style traffic patterns following npm installs.
• Where possible, restrict npm install execution in CI to sandboxed, network-egress-limited environments, and consider disabling install-time lifecycle scripts (--ignore-scripts) for untrusted packages.

Developing intel

This is a fast-moving, net-new supply-chain campaign report without an associated CVE, and details on package names, IOCs, and RedC2's full capabilities may still be emerging. Defenders should treat this summary as preliminary and consult the original reporting for the latest specifics: The Hacker News: 14 Trojanized npm Packages Drop RedC2 4.0 Linux Backdoor With AI-Assisted C2.