Malicious code in @ecg-internal/media-util-js-lib (npm)

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

Source: amazon-inspector (c716438d9014063b4616588b1522ba2de2f3cf4fd961212840ed6a324cced3da)

The package publishes to the public npm registry under the scoped name @ecg-internal/media-util-js-lib, which resembles an internal namespace. It ships no real functionality — the main entry exports a Proxy stub returning no-ops for every property, described as a 'Compatibility shim.' Both package.json postinstall (node beacon.cjs) and the main module invoke fire() in beacon.cjs, which POSTs the installer's hostname (os.hostname()), install path (__dirname), current working directory (process.cwd()), Node version, and package name to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over cleartext HTTP. The beacon fires on npm install without user action and again whenever the module is required, so any internal build system misconfigured to resolve this public artifact for an @ecg-internal/* dependency transmits identifying host and path information to the attacker-controlled endpoint. The 'build-provenance beacon' comment in the source is a cover story inconsistent with the hardcoded bare-IP destination unrelated to any legitimate publisher infrastructure.

Source: ghsa-malware (32be042c37e2c4ebd8edb68e47d68af04056c09e3c1d5e087f78c934f0d567e7)

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.