supply chain event / NVI-00008441 / Revision 1
Malicious code in @greenlake/common-context (npm)
GitHub lists this malware advisory for @greenlake/common-context, @greenlake/common-context. 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/common-context
source listed= 99.0.1
## Source: amazon-inspector (5c391fc0f0acc51479adc96cdca5e63497f47dd4304eb0a871819bce9313551e) @greenlake/common-context@99.0.1 is a stub package whose main entry exports a Proxy of no-op functions and whose only real behavior is a beacon. Both scripts.postinstall (node beacon.cjs) and require() of the main entry (index.js) POST host identifiers — package name, os.hostname(), __dirname install path, process.cwd(), and node version — to the hardcoded bare-IP plaintext endpoint http://185.158.107.175:8787/_ah/dc. The destination is not registry or publisher infrastructure. Combined with the @greenlake scope, implausibly high 99.0.1 version, generic 'Compatibility shim' description, and no-op Proxy main, the package matches the canonical dependency-confusion payload shape: a lure designed to be auto-resolved in place of an internal private name and to callback-report successful installations inside the target environment. --- Credit: OpenSSF (source)
@greenlake/common-context
source listed= 3.0.0
## Source: amazon-inspector (5c391fc0f0acc51479adc96cdca5e63497f47dd4304eb0a871819bce9313551e) @greenlake/common-context@99.0.1 is a stub package whose main entry exports a Proxy of no-op functions and whose only real behavior is a beacon. Both scripts.postinstall (node beacon.cjs) and require() of the main entry (index.js) POST host identifiers — package name, os.hostname(), __dirname install path, process.cwd(), and node version — to the hardcoded bare-IP plaintext endpoint http://185.158.107.175:8787/_ah/dc. The destination is not registry or publisher infrastructure. Combined with the @greenlake scope, implausibly high 99.0.1 version, generic 'Compatibility shim' description, and no-op Proxy main, the package matches the canonical dependency-confusion payload shape: a lure designed to be auto-resolved in place of an internal private name and to callback-report successful installations inside the target environment. --- Credit: OpenSSF (source)
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-p5fc-j294-qr5q ↗
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.