supply chain event / NVI-00012195 / Revision 1
Malicious code in chat-adapter-matrix (npm)
GitHub lists this malware advisory for chat-adapter-matrix. 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.
chat-adapter-matrix
source listed= 99.99.99
## Source: amazon-inspector (5710eb2e1a2f6b7a4aca8d943953989e80e056cc77c2071027c2a78744b5ea3a) chat-adapter-matrix@99.99.99 executes server.js from every npm lifecycle hook (preinstall, install, postinstall, prepare, prepublish, preprepare, postprepare) and from the main module. server.js issues an HTTPS GET to the hardcoded webhook host eo8f3m3ho26a0nm.m.pipedream.net with the package name embedded in the URL path (https://eo8f3m3ho26a0nm.m.pipedream.net/vercel/). The receiving Pipedream endpoint captures the source IP, hostname context, and confirmation that this squatted name was resolved and installed. The implausibly high 99.99.99 version and the embedded 'Proof by @0xWise' string are consistent with a dependency-confusion payload designed to win version resolution against an internal package of the same name and beacon successful installs on internal build systems to the researcher/attacker's collector. --- 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-2rg8-m9rx-gfhf ↗
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.