MAL-2026-17701 Malicious code in @kxafunc/xbails (npm)
Malicious package
Published
MAL-2026-17701 is a malicious package: @kxafunc/xbails (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-17701/ (Markdown: https://insights.sbomify.com/MAL-2026-17701/index.md)
- Package
- @kxafunc/xbails
- Registry
- npm
What is MAL-2026-17701?
MAL-2026-17701 is a malicious package in @kxafunc/xbails, published on 8 Oct 2026.
Official description
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.What should I do about MAL-2026-17701?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.