MAL-2026-18318: Malicious code in @greenlake/mfe-login-url (npm)

@greenlake/mfe-login-url 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 (2.0.0, 1.0.0, 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.

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

Source: amazon-inspector (8669a0a99995d7a57a13210e4b7e8fe8449f746ab808271370776d072491b3db) @greenlake/mfe-login-url 2.0.0 presents itself as an empty compatibility shim but ships a beacon.cjs that POSTs installer hostname, install path, cwd, and Node version to the hardcoded plain-HTTP bare-IP endpoint http://185.158.107.175:8787/ah/dc. The beacon fires in two places: package.json declares a postinstall script running node beacon.cjs, and index.js (a Proxy-based no-op stub designed not to break bundlers) invokes require('./beacon.cjs').fire() on import. The scope @greenlake and the stub-plus-beacon shape are consistent with a dependency-confusion reconnaissance package that silently confirms successful installs inside internal build systems and discloses host identifiers to an unknown operator. There is no legitimate functional code; the entire package exists to exfiltrate installer host metadata.

Source: ghsa-malware (9faa9e9c53efcfe969b4aaa5d2f8df7a5ab2879ab08cc2639f1c385dc1883094) 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.