supply chain event / NVI-00008540 / Revision 1
Malicious code in @greenlake/session (npm)
GitHub lists this malware advisory for @greenlake/session, @greenlake/session, @greenlake/session, @greenlake/session. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
@greenlake/session
source listed= 99.0.1
## Source: amazon-inspector (3255cc4148a62c7ba090d1912d41c572f3ce7ccb6db9cc131132cfd4a0970f43) The package is a scoped-namespace shim (version 99.0.1) whose main entry re-exports a Proxy returning no-op functions, allowing consumer builds to resolve this name without errors. On `npm install` (postinstall hook) and on `require('@greenlake/session')` (main-module side effect), beacon.cjs issues a plain-HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc carrying a JSON payload containing os.hostname(), __dirname (install path), process.cwd(), and process.version. The inflated version number, scoped name mimicking an internal namespace, Proxy no-op surface, and automatic beacon on both install and import together form a dependency-confusion exfiltration shape: any build that resolves @greenlake/session from the public registry instead of the intended private source leaks internal host identifiers and install locations to the hardcoded endpoint. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/b711d7c76f98b5044512e8c851547e8a05b2f959/osv/malicious/npm/@greenlake/session/MAL-2026-1828
@greenlake/session
source listed= 3.0.0
## Source: amazon-inspector (3255cc4148a62c7ba090d1912d41c572f3ce7ccb6db9cc131132cfd4a0970f43) The package is a scoped-namespace shim (version 99.0.1) whose main entry re-exports a Proxy returning no-op functions, allowing consumer builds to resolve this name without errors. On `npm install` (postinstall hook) and on `require('@greenlake/session')` (main-module side effect), beacon.cjs issues a plain-HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc carrying a JSON payload containing os.hostname(), __dirname (install path), process.cwd(), and process.version. The inflated version number, scoped name mimicking an internal namespace, Proxy no-op surface, and automatic beacon on both install and import together form a dependency-confusion exfiltration shape: any build that resolves @greenlake/session from the public registry instead of the intended private source leaks internal host identifiers and install locations to the hardcoded endpoint. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/b711d7c76f98b5044512e8c851547e8a05b2f959/osv/malicious/npm/@greenlake/session/MAL-2026-1828
@greenlake/session
source listed= 1.0.0
## Source: amazon-inspector (3255cc4148a62c7ba090d1912d41c572f3ce7ccb6db9cc131132cfd4a0970f43) The package is a scoped-namespace shim (version 99.0.1) whose main entry re-exports a Proxy returning no-op functions, allowing consumer builds to resolve this name without errors. On `npm install` (postinstall hook) and on `require('@greenlake/session')` (main-module side effect), beacon.cjs issues a plain-HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc carrying a JSON payload containing os.hostname(), __dirname (install path), process.cwd(), and process.version. The inflated version number, scoped name mimicking an internal namespace, Proxy no-op surface, and automatic beacon on both install and import together form a dependency-confusion exfiltration shape: any build that resolves @greenlake/session from the public registry instead of the intended private source leaks internal host identifiers and install locations to the hardcoded endpoint. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/b711d7c76f98b5044512e8c851547e8a05b2f959/osv/malicious/npm/@greenlake/session/MAL-2026-1828
@greenlake/session
source listed= 2.0.0
## Source: amazon-inspector (3255cc4148a62c7ba090d1912d41c572f3ce7ccb6db9cc131132cfd4a0970f43) The package is a scoped-namespace shim (version 99.0.1) whose main entry re-exports a Proxy returning no-op functions, allowing consumer builds to resolve this name without errors. On `npm install` (postinstall hook) and on `require('@greenlake/session')` (main-module side effect), beacon.cjs issues a plain-HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc carrying a JSON payload containing os.hostname(), __dirname (install path), process.cwd(), and process.version. The inflated version number, scoped name mimicking an internal namespace, Proxy no-op surface, and automatic beacon on both install and import together form a dependency-confusion exfiltration shape: any build that resolves @greenlake/session from the public registry instead of the intended private source leaks internal host identifiers and install locations to the hardcoded endpoint. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/b711d7c76f98b5044512e8c851547e8a05b2f959/osv/malicious/npm/@greenlake/session/MAL-2026-1828
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-ph7p-r8mj-5q6r ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.