Malicious code in ccl-global-shopping (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 (4f380c5b8a8363f9bdd4b9466bdbbeaed301ef5fe0facf7f64eb3296848f9f96) package.json declares its sole dependency `ltidisafe` as a direct HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.4.tgz) instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL currently serves and runs any lifecycle scripts inside the fetched package, with no version pin and no integrity hash — the bucket owner controls the code executed on every installer's machine, and the content can be swapped at any time. The package's own shipped index.js is an empty stub (`module.exports = {};`), so the manifest URL is effectively the entire payload surface. The package name resembles a shopping/retail library, giving it the shape of a dependency-confusion or typosquat lure whose only install-time effect is to pull in attacker-controlled code from an off-registry location.…

Published by the source

20 Oct 2026, 03:43 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-18061

2. Revision 2 · amended · 28 Oct 2026

   Amended from osv record MAL-2026-18061

3. Revision 1 · created · 26 Oct 2026

   Published from osv record MAL-2026-18061

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

# Patch Next advisory brief: GHSA-hh3m-f424-g8v5

Advisory: Malicious code in ccl-global-shopping (npm)
IDs: GHSA-hh3m-f424-g8v5
Record: https://patchnext.com/advisories/mal-2026-18061 (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 ccl-global-shopping: affected every version

## Suggested inspection (read-only)
- `npm ls ccl-global-shopping --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 ccl-global-shopping.
- 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-18061 (OSV record MAL-2026-18061 lists affected ranges: npm ccl-global-shopping >=99.9.1 <=99.9.1)
- Verified: https://osv.dev/vulnerability/MAL-2026-18061 (OSV record MAL-2026-18061 lists affected ranges: npm ccl-global-shopping >=0)

Commands are suggestions: review each one before running it.