NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @bellaxchan published 10 malicious packages. See the full campaign →
Malicious package

@bellaxchan/wbailsnpm

Advisory published Updated

@bellaxchan/wbails is a confirmed malicious npm package (MAL-2026-20183) that executes malicious code on install (malicious versions 1.8.2, 1.8.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @bellaxchan/wbails (npm)

MAL-2026-20183
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @bellaxchan/wbails

What this malware does

package.json declares a runtime dependency libsignal with the value github:tenka-san/libsignal-node, an off-registry git source with no commit SHA, no tag, and no integrity check. npm install @bellaxchan/[email protected] resolves this dependency to whatever bytes currently sit on the default branch of that GitHub repository and executes any lifecycle scripts the fetched tree contains. The content of the target repository can be changed at any time by whoever controls it, so install-time behavior for consumers of this package is not fixed by the published tarball. The target repository owner (tenka-san) does not match the publishing scope (@bellaxchan), so a third-party controls the executed code path.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged
1.8.21.8.3

Indicators of compromise (SHA-256)

15e4829620d3d29ef2631e9b538553e381856033d06f0ecd7814c6693586fdec
48ed9ee82156ec2dbc4c76960bf6186cb1c9f899f74a3cabdb739b3bf16c8f09
a9d7ffaf0110eadd658b38727e990a8d4fb85c57910e4abaf2d2dd9a31c5b977

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @bellaxchan/wbails (2 malicious versions).

  2. If you installed it — respond

    Remove @bellaxchan/wbails 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.

  3. Did it already run?

    If @bellaxchan/wbails 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. @bellaxchan/wbails on npm has been identified as a malicious package (versions 1.8.2, 1.8.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jxq3-wr67-vjq2IN-MAL-2026-022839IN-MAL-2026-022838

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @bellaxchan/wbails-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.

Explore

@bellaxchan/wbails (npm) malicious package — MAL-2026-20183 | O3 Security