@greenlake/mfe-login-url
Temporary package placeholder for staged publishing
This report shows the evidence for @greenlake/mfe-login-url@0.0.0-stage. 5 of 6 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 6d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18318 confirms this npm version as malicious.
Advisory
MAL-2026-18318
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @greenlake/mfe-login-url (npm)
Details
@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.
---
## 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.
References
Independent LPM AI assessment
CleanIndependent AI assessment: clean. LPM AI assessed this version as clean; the assessments disagree.
The manifest identifies this as a temporary placeholder and declares no executable entry points or lifecycle scripts. The package snapshot contains no source code that could perform package actions.
Static reason
No blocking static signals were detected.
Trigger
None; the manifest declares no lifecycle scripts or executable entry points.
Impact
No package behavior with security impact was identified.
Mechanism
The package contains only a placeholder manifest and README, with no executable code.
AI rationale
The manifest identifies this as a temporary placeholder and declares no executable entry points or lifecycle scripts. The package snapshot contains no source code that could perform package actions.
Independent scan evidence
public snapshotAI called this Clean at 99.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest marks this as a temporary placeholder and declares no lifecycle scripts or executable entry points.
- The README describes this version as a temporary placeholder awaiting a staged release.
- The package snapshot contains only package.json and README.md; no executable source files were present.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
2 flaggedpackage.jsonView file
1{
"name": "@greenlake/mfe-login-url",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
High
Suspicious Lifecycle Evidence
The manifest marks this as a temporary placeholder and declares no lifecycle scripts or executable entry points.
package.jsonView on unpkg · L1README.mdView file
1# Temporary Holding Version
This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
High
Ai Review Evidence
The README describes this version as a temporary placeholder awaiting a staged release.
README.mdView on unpkg · L1Findings
2 High1 Low
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review EvidenceREADME.md
LowNo License
Affected versions and remediation
This report applies to @greenlake/mfe-login-url@0.0.0-stage.
The versions list below shows the verdict for each recorded version.
- Avoid installing @greenlake/mfe-login-url@0.0.0-stage. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.