Malicious code in sc-announcer (npm)

---

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (2a03b9445f383410d981355df7ba577b7834a37d226e05852b4a0b9c7d998d9c)

sc-announcer@99.9.1 ships an empty stub (module.exports = {}) and declares a single dependency ltidisafe sourced from an off-registry HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.2.tgz) in package.json rather than a registry version range. On npm install, npm fetches that tarball and installs whatever bytes it returns, with no version pin, no integrity hash, and no registry provenance; any lifecycle scripts contained inside the fetched tarball execute on the installer's machine. The implausibly high version number (99.9.1) and dependency-confusion-shaped setup — stub package whose only effect is to pull a URL-sourced dependency — are consistent with a resolution-hijack lure targeting an internal package name.

Source: ghsa-malware (d9ead28d049c543c5524678b075f42d3d7aa26d6d7e12e58e44244651501f6f0)

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 (38abcbba47f18b6d76a06a770258c620fc322472d0db0d38b67f04805b916d43)

The OpenSSF Package Analysis project identified 'sc-announcer' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

• The package communicates with a domain associated with malicious activity.