Malicious code in @greenlake/session (npm)
Exact source revision recorded 26 Oct 2026 06:21:11 UTC. It does not establish the source's current position. Latest evidence.
osv · MAL-2026-18283
Published@greenlake/session 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, 99.0.1, 1.0.0, 2.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 (57df84a0164eda463123b80b9c0b871e6aeedaf39bfb0f585641495fd9b7c25c) The package is a near-empty shim whose only functional behavior is a beacon. beacon.cjs defines a hardcoded bare-IP HTTP endpoint (http://185.158.107.175:8787/_ah/dc) and a fire() routine that POSTs installer-side host identifiers to it: package name, os.hostname(), __dirname (install path), process.cwd(), and process.version. fire() is invoked from the postinstall lifecycle script, so it runs automatically on `npm install`, and also from the main entry, so it runs again on `require('@greenlake/session')`. The main export is a Proxy that returns a no-op for every property access, so the package provides no legitimate functionality. The README self-labels this as an authorized dependency-confusion test against an internal `@greenlake` scope, but that is author-controlled text and does not constitute consent from any other installer whose resolver pulls this public package in place of the intended internal one. The data path is unencrypted (plain HTTP) and the destination is a bare IP unrelated to any declared publisher infrastructure.
- Source published
- 23 Oct 2026 21:35:48 UTC
- Source modified
- 26 Oct 2026 06:00:04 UTC
- Observed here
- 26 Oct 2026 06:21:11 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.