Malicious code in @cecm-web-sdk/core (npm)

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

Source: amazon-inspector (01486f39bf686dc3adf20501374bdaa430fab9a7125a995cd63352e3d50c3bad)

The package has no functional code: its declared main (index.js) exports a Proxy whose property access returns no-op functions, and the package describes itself as a 'Compatibility shim'. On npm install, the postinstall lifecycle hook (node beacon.cjs) runs and POSTs a payload containing the package name, OS hostname, install directory, current working directory, and Node version to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over plain HTTP. index.js additionally invokes beacon.cjs::fire() at top level, so requiring or importing the module triggers the same beacon a second time, which fires even when installs run with --ignore-scripts. The scope-prefixed name combined with host/path identification is the canonical dependency-confusion recon success-ping, enabling the operator of 185.158.107.175 to identify internal hosts and project paths where this name resolves to the public registry copy.

Source: ghsa-malware (95975e46912705ce591acef6b00c3b11b9dcf9f6ea8f1f89840a77a3ec6134d4)

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.