Which versions of zabittest11 are malicious?

The following npm versions of zabittest11 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate zabittest11 if I installed it?

Remove zabittest11 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 zabittest11 — how do I know if it already compromised me?

If zabittest11 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 zabittest11 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zabittest11 (version 1.0.1).

Malicious package

zabittest11npm

Advisory published Jan 25, 2026Updated Feb 2, 2026

zabittest11 is a confirmed malicious npm package (MAL-2026-500) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zabittest11 (npm)

MAL-2026-500

Immediate action

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

npm uninstall zabittest11

What this malware does

The package zabittest11 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'zabittest11' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

3599364ab8220ed1b88dd539b35b7f8e94d8d124030b13fc98b5e0daa7657032

08a0084877b46812f2b43eaa232ecb1768d4b4415111ee65c741f2cc7acfa784

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zabittest11 (version 1.0.1).
If you installed it — respond
Remove zabittest11 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 zabittest11 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. zabittest11 on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks zabittest11-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