@greenlake/context-pane@0.0.0-stage
Temporary package placeholder for staged publishing
OpenSSF/OSV Malicious Advisory
imported 6d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18317 confirms this npm version as malicious.
Advisory
MAL-2026-18317
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @greenlake/context-pane (npm)
Details
@greenlake/context-pane 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, 1.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 (b7f6299b80d36c1d11d7a258c9bffdeb2e1281348e599487c011dd9e959d7120) The package declares a postinstall script (beacon.cjs) and a main entry (index.js) that both invoke a beacon POSTing the installer's hostname, install path, cwd, and node version to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over cleartext HTTP. The destination is a bare IPv4 on a non-standard port, unrelated to any publisher infrastructure. The package has no advertised functionality: main exports a Proxy of no-op functions so that bundlers and consumers do not crash on property access, while the require-time path and the postinstall hook both exist solely to trigger the callback. The package self-describes as a 'Compatibility shim' with no legitimate reason to phone home, and the generic @greenlake/context-pane name combined with the no-op export surface is consistent with a dependency-confusion lure whose only effect on installers is the install-time and import-time beacon.
## Source: ghsa-malware (193d0e8c4b04c5227f73248853240c294e6799cc482fbbd7fa57c27257a21248) 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.
Independent LPM AI assessment
CleanIndependent AI assessment: clean. LPM AI assessed this version as clean; the assessments disagree.
The manifest declares no scripts, entry points, binaries, or dependencies, and the only other file describes the package as a temporary placeholder. No executable behavior or attack was identified.
Static reason
No blocking static signals were detected.
Trigger
No executable entry point or lifecycle script is declared.
Impact
No package behavior capable of harming users was identified.
Mechanism
The package contains only manifest and README text, with no code that performs actions.
AI rationale
The manifest declares no scripts, entry points, binaries, or dependencies, and the only other file describes the package as a temporary placeholder. No executable behavior or attack was identified.
Independent scan evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares only the package name, version, stub marker, and placeholder description; it has no lifecycle scripts, entry points, binaries, or dependencies.
- The package contains only package.json and README.md; the README describes it as a temporary placeholder.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
2 flaggedpackage.jsonView file
•Published source reference
High
Suspicious Lifecycle Evidence
package.json declares only the package name, version, stub marker, and placeholder description; it has no lifecycle scripts, entry points, binaries, or dependencies.
package.jsonView on unpkg•Published source reference
High
Ai Review Evidence
The package contains only package.json and README.md; the README describes it as a temporary placeholder.
package.jsonView on unpkgFindings
2 High1 Low
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencepackage.json
LowNo License
Affected versions and remediation
This report applies to @greenlake/context-pane@0.0.0-stage.
See all versions of @greenlake/context-pane for other recorded verdicts.
- Avoid installing @greenlake/context-pane@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.