Malicious code in @ecg-internal/aurora-js-formatters (npm)

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

Source: amazon-inspector (02325fb617beffd55194047faca7300b33934cd471de94bab66a24954200cba0)

The package uses an internal-looking scope (@ecg-internal) and an implausibly high version (99.0.1) consistent with dependency-confusion targeting. On install, the declared postinstall script executes beacon.cjs, which POSTs a JSON payload containing the package name, os.hostname(), __dirname install path, process.cwd(), and process.version to the hardcoded plain-HTTP bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The main entry index.js additionally invokes beacon.cjs.fire() at top level on require/import, so the callback also fires when the module is loaded by a bundler or build process even if lifecycle scripts are disabled with --ignore-scripts. index.js exports a Proxy of no-op functions so consuming code and bundlers do not fail, allowing the beacon to run silently inside build pipelines. The destination IP is unrelated to any publisher infrastructure and has no TLS. The payload identifies the installing host and build environment to the operator of that endpoint, enabling enumeration of internal environments that resolved this scoped name from the public registry.

Source: ghsa-malware (a62187d1781539a34c8628cdf04cf2797250060a55eddcc1736b7f04b21b5bfa)

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.