Malicious code in @capsense/ccx-welcome-page (npm)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (0f63b73ae5e707b0eecee16f97f8ab26b350d135547448fbf6e005ba33303060) The package publishes under the @capsense scope at version 99.99.100 and wires all three npm lifecycle hooks (preinstall, install, postinstall) to run beacon.js. beacon.js collects os.hostname(), os.userInfo(), and os.platform() and sends the installer's hostname, username, and OS to two hardcoded attacker-controlled collectors: a DNS lookup against the Interactsh OAST subdomain dbf2v9d8dg559apcd93guf6i7uxrn5coo.oast.pro and an HTTPS GET to webhook.site/59675304-bec1-4ca0-8409-8d37b65ec116 with the host identity in the query string. The scope+version combination (public @capsense scope, implausibly high 99.99.100) is the canonical dependency-confusion shape, intended to override a private internal @capsense package during resolution and fire the beacon on any internal build that pulls the public version. The self-label as a…

Published by the source

25 Oct 2026, 18:19 UTC

Last modified by the source

29 Oct 2026, 14:30 UTC

Source last checked

30 Oct 2026, 06:15 UTC

1. Revision 4 · amended · 30 Oct 2026

   Amended from osv record MAL-2026-18294

2. Revision 3 · amended · 29 Oct 2026

   Amended from osv record MAL-2026-18294

3. Revision 2 · amended · 27 Oct 2026

   Amended from osv record MAL-2026-18294

4. Revision 1 · created · 26 Oct 2026

   Published from osv record MAL-2026-18294

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

# Patch Next advisory brief: GHSA-phgq-4c2g-6xpx

Advisory: Malicious code in @capsense/ccx-welcome-page (npm)
IDs: GHSA-phgq-4c2g-6xpx
Record: https://patchnext.com/advisories/mal-2026-18294 (revision 4, source checked 30 Oct 2026, 06:15 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 @capsense/ccx-welcome-page: affected every version

## Suggested inspection (read-only)
- `npm ls @capsense/ccx-welcome-page --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 @capsense/ccx-welcome-page.
- 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/MAL-2026-18294 (OSV record MAL-2026-18294 lists affected ranges: npm @capsense/ccx-welcome-page >=99.99.100 =99.99.99 <=99.99.99)
- Verified: https://osv.dev/vulnerability/MAL-2026-18294 (OSV record MAL-2026-18294 lists affected ranges: npm @capsense/ccx-welcome-page >=0)

Commands are suggestions: review each one before running it.