Malicious code in @ecg-internal/js-react-i18n (npm)

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

Source: amazon-inspector (533583f613bf03556a1660b5bd8eaf4d5899c96dc79f4c42ae6b883aea8fde0e)

The package is published under an internal-looking scope (@ecg-internal) and ships a stub main module that returns a Proxy of no-op functions for every property access — it provides none of the i18n functionality its name implies. Its only real behavior is firing beacon.cjs, which executes both from the declared postinstall lifecycle script (node beacon.cjs) and from a top-level require('./beacon.cjs').fire() in the main module. beacon.cjs collects the installer's hostname (via os.hostname()), install path (__dirname), current working directory, Node.js version, and package name, and POSTs them over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The destination is not a publisher-aligned domain and the shape — internal-looking scope + hollow functional surface + install- and import-time callback with host identifiers to a bare IP — is a dependency-confusion reconnaissance probe designed to identify internal build systems that resolve the private name from the public registry.

Source: ghsa-malware (4b6637975491d2cb9a6fe062dab13216afeeeda88e533e8cfde6d628df841bf5)

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.