Which versions of @zalastax/nolb-cc2 are malicious?

Every published version of @zalastax/nolb-cc2 on npm is considered malicious. Remove the package entirely.

How do I remediate @zalastax/nolb-cc2 if I installed it?

@zalastax/nolb-cc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @zalastax/nolb-cc2 — how do I know if it already compromised me?

If @zalastax/nolb-cc2 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @zalastax/nolb-cc2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @zalastax/nolb-cc2 (all published versions).

Part of a larger attack: @zalastax published 4544 malicious packages. See the full campaign →

Malicious package

@zalastax/nolb-cc2npm

Advisory published Aug 14, 2025Updated Aug 14, 2025

@zalastax/nolb-cc2 is a confirmed malicious npm package (MAL-2025-10869) that opens a backdoor for remote access. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zalastax/nolb-cc2 (npm)

MAL-2025-10869

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @zalastax/nolb-cc2

What this malware does

The package @zalastax/nolb-cc2 was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @zalastax/nolb-cc2 (all published versions).
If you installed it — respond
@zalastax/nolb-cc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @zalastax/nolb-cc2 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @zalastax/nolb-cc2 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zalastax/nolb-cc2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database