Malicious code in @kxafunc/xbails (npm)

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (629c665fbfef767c56d24af935d38312f7aa88d1c71d9dfb8c427192e54add0b) 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.

Source published

8 Oct 2026 17:47:11 UTC

Source modified

8 Oct 2026 18:30:05 UTC

Observed here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.