Malicious code in @greenlake/mfe-login-url (npm)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

@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…

Published by the source

23 Oct 2026, 21:33 UTC

Last modified by the source

29 Oct 2026, 14:45 UTC

Source last checked

30 Oct 2026, 06:00 UTC

1. Revision 3 · amended · 30 Oct 2026

   Amended from osv record MAL-2026-18318

2. Revision 2 · amended · 27 Oct 2026

   Amended from osv record MAL-2026-18318

3. Revision 1 · created · 26 Oct 2026

   Published from osv record MAL-2026-18318

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-6vg7-x7p2-c749

Advisory: Malicious code in @greenlake/mfe-login-url (npm)
IDs: GHSA-6vg7-x7p2-c749
Record: https://patchnext.com/advisories/mal-2026-18318 (revision 3, source checked 30 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @greenlake/mfe-login-url: affected every version

## Suggested inspection (read-only)
- `npm ls @greenlake/mfe-login-url --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @greenlake/mfe-login-url.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-18318 (OSV record MAL-2026-18318 lists affected ranges: npm @greenlake/mfe-login-url >=2.0.0 =1.0.0 =3.0.0 <=3.0.0)
- Verified: https://osv.dev/vulnerability/MAL-2026-18318 (OSV record MAL-2026-18318 lists affected ranges: npm @greenlake/mfe-login-url >=0)

Commands are suggestions: review each one before running it.