@greenlake/common-context@0.1.0

@greenlake/common-context is a dependency-confusion package: it is described as a "Compatibility shim", uses inflated version numbers, and its README calls it an "authorized dependency-confusion test". Each listed version (99.0.1, 3.0.0) has a postinstall script that runs `node beacon.cjs` on npm install, and index.js calls the same code when the package is imported; it POSTs the hostname, install path and current working directory over plain HTTP to `http://185.158.107.175:8787/_ah/dc`, and index.js exports a Proxy that returns no-op functions so builds importing the real package keep running. The npm account wiseke published 14 such packages under the @greenlake, @sxm-web, @drone-js-ext and @ppa-web-components scopes between 2026-10-23 21:23 and 2026-10-25 14:28 UTC; index.js is byte-identical to that of ph-common (MAL-2026-1809), which sends to the same endpoint. --- ## Source: amazon-inspector (8ee1e5c23e641cce920808500ad850f4965adeb982b4c14233901c80c2cfb039) The package self-describes as a 'Compatibility shim' and exports an inert Proxy that returns no-op functions for every property, providing no functional API. Its only runtime behavior is a beacon in beacon.cjs that fires both from the npm postinstall lifecycle hook and on require() via index.js. The beacon collects the installer's OS hostname, __dirname install path, and process.cwd() (which commonly embed the Unix username and internal project/repo names) along with Node version, and POSTs them as JSON to the hardcoded plaintext bare-IP endpoint http://185.158.107.175:8787/_ah/dc with an x-beacon-package header identifying the resolving package. The scoped name @greenlake/* mimicking an internal namespace, the inert public API, and the automatic callback to a hardcoded bare-IP operator on install and import together match the shape of a dependency-confusion probe: resolving this package on an installer's machine silently discloses internal host, user, path, and namespace information to an external operator the installer did not opt into. ## Source: ghsa-malware (09b757ef91607a1bfe1b7e02eb0fc5e2d2647503898e30d04769ac1a5fc5385b) 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.