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/wabailsnpm

Advisory published Updated

@bellaxchan/wabails is a confirmed malicious npm package (MAL-2026-20182) that executes malicious code on install (malicious version 1.7.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @bellaxchan/wabails (npm)

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

What this malware does

package.json declares the dependency libsignal with the value npm:bellaxchan/libsignal-node, which npm resolves at install time by fetching the current contents of the GitHub repository bellaxchan/libsignal-node. No version tag, branch, or commit SHA is pinned and no integrity hash is checked, so npm install downloads whatever bytes currently sit at that location and runs any lifecycle scripts inside them on the installer's machine. Whoever controls that GitHub account controls the code executed during every install of this package, making the dependency resolution itself the install-time execution vector regardless of the current repository contents.

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

1 flagged
1.7.3

Indicators of compromise (SHA-256)

0ff6c20fca2b5b0b16cd035582ce321123ee9b6380dc565e4c544054a0823626
aed8ba752263403243608bd9df0e0b340e3c0210a1e787f05801e4d7945ebefa

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @bellaxchan/wabails (version 1.7.3).

  2. If you installed it — respond

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

Campaign

GHSA-p99r-cq2r-f4rvIN-MAL-2026-022837

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @bellaxchan/wabails-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/wabails (npm) malicious package — MAL-2026-20182 | O3 Security