Malicious code in @capsense/core-ui (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 (cd830a923fd6fbe61525c9d152a75384cbd42624a45edc957c2f055ff8fa61a8) @capsense/core-ui@99.99.100 is published to the public npm registry under a scoped name at an implausibly high version, a shape used to override an organization's internal package of the same scope during resolution. The package's package.json declares preinstall, install, and postinstall lifecycle scripts that all invoke `node beacon.js`. beacon.js uses `os.hostname()`, `os.userInfo()`, and `os.platform()` to collect the installer's hostname, username, and platform, and transmits those identifiers to two attacker-controlled collectors: a subdomain of oast.pro (dbf2v9d8dg559apcd93guf6i7uxrn5coo.oast.pro) via DNS lookup and HTTPS GET, and webhook.site via query string. The beacon fires automatically on every `npm install`, before any code review of the package contents. Framing in the package description as a disclosure/PoC does not…

Published by the source

25 Oct 2026, 18:54 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-18295

2. Revision 3 · amended · 29 Oct 2026

   Amended from osv record MAL-2026-18295

3. Revision 2 · amended · 27 Oct 2026

   Amended from osv record MAL-2026-18295

4. Revision 1 · created · 26 Oct 2026

   Published from osv record MAL-2026-18295

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

# Patch Next advisory brief: GHSA-c2qc-c78r-386v

Advisory: Malicious code in @capsense/core-ui (npm)
IDs: GHSA-c2qc-c78r-386v
Record: https://patchnext.com/advisories/mal-2026-18295 (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/core-ui: affected every version

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

Commands are suggestions: review each one before running it.