Which versions of @kxafunc/xbails are malicious?

The following npm versions of @kxafunc/xbails are flagged malicious: 0.0.8. Treat any of these as compromised.

How do I remediate @kxafunc/xbails if I installed it?

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

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

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

Search your lockfiles and build artifacts for @kxafunc/xbails (version 0.0.8).

Malicious package

@kxafunc/xbailsnpm

Advisory published Oct 8, 2026Updated Oct 8, 2026

@kxafunc/xbails is a confirmed malicious npm package (MAL-2026-17701) that executes malicious code on install (malicious version 0.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @kxafunc/xbails (npm)

MAL-2026-17701

Immediate action

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

npm uninstall @kxafunc/xbails

What this malware does

package.json aliases the libsignal dependency to npm:@bellaxchuu/libsignal-node@latest — a non-standard publisher pinned to the mutable latest dist-tag with no version pin, no integrity check, and no hash. On every install, npm resolves this alias to whatever bytes @bellaxchuu/libsignal-node currently publishes, and the resolved module is loaded by lib/Signal/libsignal.js and lib/Utils/crypto.js, providing the Signal end-to-end cryptographic primitives (SessionCipher, SessionBuilder, ProtocolAddress, SessionRecord) with access to identity keys, prekeys, and plaintext messages. Whoever controls that upstream package name can push arbitrary code into every installer at any time, executing inside the Signal E2E encrypt/decrypt path. This is an off-registry-style trust relationship: the manifest itself constitutes the exposure, independent of what the current contents of the alias target happen to be.

Malicious versions

1 flagged

0.0.8

Indicators of compromise (SHA-256)

629c665fbfef767c56d24af935d38312f7aa88d1c71d9dfb8c427192e54add0b

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-021228

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @kxafunc/xbails-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