Which versions of @wanzforme/bails4u are malicious?

The following npm versions of @wanzforme/bails4u are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @wanzforme/bails4u if I installed it?

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

If @wanzforme/bails4u 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 @wanzforme/bails4u part of a known attack campaign?

Yes — @wanzforme/bails4u is associated with the IN-MAL-2026-022674 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 @wanzforme/bails4u across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @wanzforme/bails4u (version 1.0.0).

Malicious package

@wanzforme/bails4unpm

Advisory published Nov 13, 2026Updated Nov 13, 2026

@wanzforme/bails4u is a confirmed malicious npm package (MAL-2026-19219) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wanzforme/bails4u (npm)

MAL-2026-19219

Immediate action

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

npm uninstall @wanzforme/bails4u

What this malware does

package.json declares a runtime dependency libsignal with the source github:wanzchil/libsignal-node. The reference has no commit SHA, tag, or integrity hash, so npm install resolves whatever the referenced repository's default branch currently contains and executes any lifecycle scripts bundled with it on the installer's machine. The owner of wanzchil/libsignal-node can push new commits at any time, and future installs will fetch and run those bytes with no version pin and no verification — fully bypassing the npm registry's integrity model for this dependency. A separate static match in lib/Utils/generics.js around a ping/HTTP pattern is consistent with WhatsApp/Baileys-style network utilities and is not independently indicative of malice.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7db6d4bfe675bbaa2043f2958993761070ab6e5a09572d884082465b51bdf437

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-022674

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wanzforme/bails4u-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