{"items":[{"id":"NVI-00009813","kind":"supply_chain_event","title":"Malicious code in @kxafunc/xbails (npm)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-5prw-6f85-2mmg"],"plain_summary":"GitHub lists this malware advisory for @kxafunc/xbails. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-640d7e01b3ceb098e6b4f994175cb732"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-640d7e01b3ceb098e6b4f994175cb732","url":"https://github.com/advisories/GHSA-5prw-6f85-2mmg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5prw-6f85-2mmg","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:01.069Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-640d7e01b3ceb098e6b4f994175cb732"],"technology":"@kxafunc/xbails","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (629c665fbfef767c56d24af935d38312f7aa88d1c71d9dfb8c427192e54add0b)\npackage.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.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/5d188407124ec872abbdfa7363372d071f0ecf23/osv/malicious/n","public_affected_ranges":["= 0.0.8"]}],"null_published_at":"2026-10-31T22:13:39.948Z","source_updated_at":"2026-10-08T18:31:54.000Z","source_disclosed_at":"2026-10-08T18:31:53.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T22:07:01.069Z"}],"next_cursor":null,"snapshot_revision":"42594"}