MAL-2026-18317 Malicious code in @greenlake/context-pane (npm)

@greenlake/context-pane 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 (3.0.0, 1.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.

The package declares a postinstall script (beacon.cjs) and a main entry (index.js) that both invoke a beacon POSTing the installer's hostname, install path, cwd, and node version to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over cleartext HTTP. The destination is a bare IPv4 on a non-standard port, unrelated to any publisher infrastructure. The package has no advertised functionality: main exports a Proxy of no-op functions so that bundlers and consumers do not crash on property access, while the require-time path and the postinstall hook both exist solely to trigger the callback. The package self-describes as a 'Compatibility shim' with no legitimate reason to phone home, and the generic @greenlake/context-pane name combined with the no-op export surface is consistent with a dependency-confusion lure whose only effect on installers is the install-time and import-time beacon.

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.