Malicious code in jshelperdependenceny (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 (dc4d19697f4104351bb25b7e568018ec6ed85d626b7265fb4b9682ae12183be9) npm package 'jshelperdependenceny' is published at version 99.0.0 with a preinstall banner stating it is intended to shadow an internal v1.0.0 package of the same name — the classic dependency-confusion shape of using an inflated version to win resolution against a private registry. On install, package.json runs 'node preinstall.js || true', which collects os.hostname(), os.platform(), os.arch(), and the package name/version and POSTs them as JSON to a URL taken from the DC_CALLBACK_URL environment variable, defaulting to http://127.0.0.1:5656/exfil. The env-var override turns the loopback default into a functional attacker-configurable beacon that fires automatically on npm install and discloses installer host identifiers plus confirmation that the shadowed internal name resolved to this public artifact.

Source: ghsa-malware…

Published by the source

25 Oct 2026, 15:11 UTC

Last modified by the source

29 Oct 2026, 14:30 UTC

Source last checked

30 Oct 2026, 06:05 UTC

1. Revision 3 · amended · 30 Oct 2026

   Amended from osv record MAL-2026-18288

2. Revision 2 · amended · 27 Oct 2026

   Amended from osv record MAL-2026-18288

3. Revision 1 · created · 26 Oct 2026

   Published from osv record MAL-2026-18288

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

# Patch Next advisory brief: GHSA-2gxp-q3vq-594r

Advisory: Malicious code in jshelperdependenceny (npm)
IDs: GHSA-2gxp-q3vq-594r
Record: https://patchnext.com/advisories/mal-2026-18288 (revision 3, source checked 30 Oct 2026, 06:05 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 jshelperdependenceny: affected >= 99.0.0, <= 99.0.0; >= 1.0.0, <= 1.0.0; >= 0.0.0-stage, <= 0.0.0-stage

## Suggested inspection (read-only)
- `npm ls jshelperdependenceny --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 jshelperdependenceny.
- 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-18288 (OSV record MAL-2026-18288 lists affected ranges: npm jshelperdependenceny >=99.0.0 <=99.0.0)
- Verified: https://osv.dev/vulnerability/MAL-2026-18288 (OSV record MAL-2026-18288 lists affected ranges: npm jshelperdependenceny >=99.0.0 =1.0.0 =0.0.0-stage <=0.0.0-stage)

Commands are suggestions: review each one before running it.