Malicious code in @grabcad/company-server-shared (npm)

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (77669bd2c3c9138e7d3ab0612febc058dfd8235eb812a40ffb5bf3f27d19bf47) Package self-describes as a `Compatibility shim.` for the `@grabcad` scope and ships no real functionality: `index.js` exports a Proxy whose property access returns no-op functions, so a build importing the real `@grabcad/company-server-shared` resolves this placeholder and silently succeeds. On installation, the `postinstall` script runs `node beacon.cjs`, and `index.js` also invokes the same `fire()` routine on require. The beacon POSTs JSON containing `os.hostname()`, `__dirname` (install path), `process.cwd()`, and the Node/npm version to the hardcoded plain-HTTP bare-IP endpoint `http://185.158.107.175:8787/_ah/dc`. The combination of a scoped placeholder with no legitimate functionality, automatic install-time and require-time execution, and a hardcoded recon callback to an unrelated bare IP is the standard shape of a dependency-confusion attack targeting the private `@grabcad` scope, leaking internal hostnames and build-path metadata to an attacker-controlled destination. ## Source: ghsa-malware (2d3297d13e6357ac5ba4aec72460852436e01486aeeffe04bf868aa8ccc58ceb) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Source published

23 Oct 2026 02:05:19 UTC

Source modified

26 Oct 2026 06:00:04 UTC

Observed here

26 Oct 2026 06:21:11 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.