supply chain event / NVI-00011173 / Revision 1
Malicious code in @chatunity/baileys (npm)
GitHub lists this malware advisory for @chatunity/baileys, @chatunity/baileys. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
@chatunity/baileys
source listed= 3.2.0
## Source: amazon-inspector (b6d06d6b516b21b0ac6ed45e5653dca243695a2c17326669ec58498e4c9bcf45) package.json declares the runtime dependency `libsignal` with the value `github:chatunitycenter/libsignal-node`, an off-registry git source with no commit SHA or tag pin. On `npm install`, npm fetches whatever the default branch of that repository currently contains and executes any lifecycle scripts inside it, and the module is then required transitively via lib/Signal/libsignal.js from the package's main entry. The dependency source is mutable and integrity-unchecked: any change pushed to that branch (or takeover of the owning account) is executed on every subsequent install of this package version, with no version bump or artifact change on the npm side. The owning GitHub account is unrelated to established libsignal publishers and there is no signature or hash gating the fetched content. --- Credit: OpenSSF (source)
@chatunity/baileys
source listed= 3.2.1
## Source: amazon-inspector (b6d06d6b516b21b0ac6ed45e5653dca243695a2c17326669ec58498e4c9bcf45) package.json declares the runtime dependency `libsignal` with the value `github:chatunitycenter/libsignal-node`, an off-registry git source with no commit SHA or tag pin. On `npm install`, npm fetches whatever the default branch of that repository currently contains and executes any lifecycle scripts inside it, and the module is then required transitively via lib/Signal/libsignal.js from the package's main entry. The dependency source is mutable and integrity-unchecked: any change pushed to that branch (or takeover of the owning account) is executed on every subsequent install of this package version, with no version bump or artifact change on the npm side. The owning GitHub account is unrelated to established libsignal publishers and there is no signature or hash gating the fetched content. --- Credit: OpenSSF (source)
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-6jgr-8f9m-5rp7 ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.