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

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

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

Remove @zalastax/nolb-pasj from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If @zalastax/nolb-pasj 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-pasj across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

@zalastax/nolb-pasjnpm

Advisory published Aug 14, 2025Updated Aug 14, 2025

@zalastax/nolb-pasj is a confirmed malicious npm package (MAL-2025-13035) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2025-13035

Immediate action

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

npm uninstall @zalastax/nolb-pasj

What this malware does

The package @zalastax/nolb-pasj 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

Malicious package

Find it
Search your lockfiles and build artifacts for @zalastax/nolb-pasj (all published versions).
If you installed it — respond
Remove @zalastax/nolb-pasj from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @zalastax/nolb-pasj 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-pasj 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-pasj-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database