Malicious code in sc-hydrate-carousel-price (npm)
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.
Affected packages
npm sc-hydrate-carousel-price
- Affected
- every version
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18291 lists affected ranges: npm sc-hydrate-carousel-price >=99.9.1 <=99.9.1
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18291 lists affected ranges: npm sc-hydrate-carousel-price >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
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.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (fbcb760747e0ad33cc6bafa85914d99b141f5361c13c5c642122d1ea8f973d9f) package.json declares a dependency `ltidisafe` whose source is a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.3.tgz) rather than a registry version range. On npm install, npm fetches whatever bytes are served at that URL and installs them, running any lifecycle scripts contained in the fetched tarball. There is no version pin, no integrity hash, and no signature check, so the contents are mutable and controlled by whoever controls that storage bucket. The package's own shipped code is an inert stub (index.js is `module.exports = {};`), so the manifest line is effectively the entire delivered payload — the published package functions as a loader for externally hosted code. The implausibly high version (99.9.1) combined with the `sc-hydrate-carousel-price` name is consistent with a…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from osv record MAL-2026-18291
- Revision 2 · amended ·
Amended from osv record MAL-2026-18291
- Revision 1 · created ·
Published from osv record MAL-2026-18291
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-9gcx-88qx-rxch Advisory: Malicious code in sc-hydrate-carousel-price (npm) IDs: GHSA-9gcx-88qx-rxch Record: https://patchnext.com/advisories/mal-2026-18291 (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 sc-hydrate-carousel-price: affected every version ## Suggested inspection (read-only) - `npm ls sc-hydrate-carousel-price --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 sc-hydrate-carousel-price. - 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-18291 (OSV record MAL-2026-18291 lists affected ranges: npm sc-hydrate-carousel-price >=99.9.1 <=99.9.1) - Verified: https://osv.dev/vulnerability/MAL-2026-18291 (OSV record MAL-2026-18291 lists affected ranges: npm sc-hydrate-carousel-price >=0) Commands are suggestions: review each one before running it.
Loading voting…