Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious Package in stream-combine

GHSA-w6xj-45gv-fw35

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm stream-combine

    Affected
    >= 2.0.2, <= 2.0.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Version 2.0.2 of stream-combine has malicious code design to steal credentials and credit card information. The code searches all form elements for passwords, credit card numbers and CVC codes. It then uploads the information to a remote server using HTML links embedded in the page or form actions. If your application has Content Security Policy set you are not affected by this issue. Recommendation This package is not available on the npm Registry anymore. If you used this module and your application processed credentials or credit card information, it is possible that information was stolen. Users may consider downgrading to version 2.0.1

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-w6xj-45gv-fw35

  2. Revision 1 · created ·

    Published from osv record GHSA-w6xj-45gv-fw35

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-w6xj-45gv-fw35

Advisory: Malicious Package in stream-combine
IDs: GHSA-w6xj-45gv-fw35
Record: https://patchnext.com/advisories/ghsa-w6xj-45gv-fw35 (revision 2, source checked 26 Oct 2026, 12:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm stream-combine: affected >= 2.0.2, <= 2.0.2

## Suggested inspection (read-only)
- `npm ls stream-combine --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on stream-combine.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w6xj-45gv-fw35 (OSV record GHSA-w6xj-45gv-fw35 lists affected ranges: npm stream-combine >=2.0.2 <=2.0.2)
- Verified: https://github.com/advisories/GHSA-w6xj-45gv-fw35 (GitHub-reviewed advisory GHSA-w6xj-45gv-fw35 lists affected ranges: npm stream-combine >=2.0.2 <=2.0.2)

Commands are suggestions: review each one before running it.

Loading voting…