Malicious code in sc-hydrate-carousel-price (npm)
Exact source revision recorded 27 Oct 2026 16:44:03 UTC. It does not establish the source's current position. Latest evidence.
osv · MAL-2026-18291
Published--- _-= 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 dependency-confusion shape intended to win resolution against an internal package. ## Source: ghsa-malware (d412736edab6560cf1dd1f5cceea58c74c6364ec1bac3349003cee396cd0c16f) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 25 Oct 2026 15:04:58 UTC
- Source modified
- 27 Oct 2026 15:45:42 UTC
- Observed here
- 27 Oct 2026 16:44:03 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.