Which versions of @corexium/xbails are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for @corexium/xbails (version 0.0.7).

Malicious package

@corexium/xbailsnpm

Advisory published Nov 3, 2026Updated Nov 3, 2026

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

Malicious code in @corexium/xbails (npm)

MAL-2026-18491

Immediate action

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

npm uninstall @corexium/xbails

What this malware does

package.json aliases the import name 'libsignal' to the third-party npm package '@bellaxchuu/libsignal-node' pinned only to the mutable '@latest' dist-tag: "libsignal": "npm:@bellaxchuu/libsignal-node@latest". The code imports 'libsignal' at module load time for end-to-end-encryption primitives (SessionCipher, SessionRecord, ProtocolAddress, SessionBuilder in lib/Signal/libsignal.js and lib/Signal/curve.js). Each install resolves whatever the owner of @bellaxchuu/libsignal-node has published to @latest, with no version pin, no integrity check, and no provenance tie to the upstream libsignal-node project. The maintainer of the aliased fork therefore controls arbitrary code that runs at require/import time of this package, including inside the cryptographic session-handling path.

Malicious versions

1 flagged

0.0.7

Indicators of compromise (SHA-256)

7e3ba0508c4009825b9eb3d248094ccbf28b2a2b4dcec420d1aaa533c1594729

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-022514

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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