@kxafunc/xbails@0.0.8

Summary

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: amazon-inspector (629c665fbfef767c56d24af935d38312f7aa88d1c71d9dfb8c427192e54add0b)