Malicious code in ccl-global-shopping (npm)
The advisory, in context
-= 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.
Source: ghsa-malware (12295a816d6da88753554047f12d4055aa2b250d351c00dee34d315f3e150c19)
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: ossf-package-analysis (31f39d40e2c7700b1c070cbd26ea533789dc444daaf58e77d191f7eb10036fc9)
The OpenSSF Package Analysis project identified 'ccl-global-shopping' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
All releases from the beginning; no upper bound recorded
No fix recorded for this interval.
1 explicitly affected versions
99.9.1
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"99.9.1"
]
}