Which versions of @bb1ptest23/test-paket are malicious?

The following npm versions of @bb1ptest23/test-paket are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate @bb1ptest23/test-paket if I installed it?

Remove @bb1ptest23/test-paket 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 @bb1ptest23/test-paket — how do I know if it already compromised me?

If @bb1ptest23/test-paket 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.

Is @bb1ptest23/test-paket part of a known attack campaign?

Yes — @bb1ptest23/test-paket is associated with the IN-MAL-2026-020778 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @bb1ptest23/test-paket across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @bb1ptest23/test-paket (version 1.0.3).

Malicious package

@bb1ptest23/test-paketnpm

Advisory published Sep 28, 2026Updated Sep 30, 2026

@bb1ptest23/test-paket is a confirmed malicious npm package (MAL-2026-17201) that executes malicious code on install (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @bb1ptest23/test-paket (npm)

MAL-2026-17201

Immediate action

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

npm uninstall @bb1ptest23/test-paket

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

The OpenSSF Package Analysis project identified '@bb1ptest23/test-paket' @ 1.0.3 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

b6b02b5a41ef4b1d07f98023a6daa2629818ee31fd68a82af64c9f52f78bec6c

88718be23e6bf753453adc1110580e87b675e7881b945d419746afe4bebcfa5e

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-020778

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @bb1ptest23/test-paket-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