---
id: "GHSA-6w2v-744r-g5j5"
kind: "package"
aliases: ["GHSA-6w2v-744r-g5j5", "MAL-2026-18217"]
title: "Malicious code in @grabcad/user-license (npm)"
severity: "critical"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "@grabcad/user-license", "fixed": [], "affected": "all versions", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["malicious", "package"]
not_affected_if: []
published_at: "2026-10-23T02:05:19+00:00"
first_seen_at: "2026-10-26T20:51:50+00:00"
updated_at: "2026-10-26T21:05:48+00:00"
sources: [{"source": "osv-malicious", "url": "https://osv.dev/vulnerability/MAL-2026-18217", "first_seen_at": "2026-10-26T20:51:50+00:00"}]
---

# Malicious code in @grabcad/user-license (npm)

## Affected

- npm:@grabcad/user-license affected all versions fixed ?

## Timeline

- 2026-10-26T20:51:50+00:00 osv-malicious https://osv.dev/vulnerability/MAL-2026-18217

## From the sources

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (a248afa43b99998214621142f85910afc980f1a664c8f6a227b523984f88ea49)
The package ships a `beacon.cjs` module that is wired to run both automatically on install (via `package.json` `postinstall: node beacon.cjs`) and on every load of the package (`index.js` calls `require('./beacon.cjs').fire()` at module top level). The beacon POSTs a JSON payload containing the installer's hostname, install directory, current working directory, and Node.js version to the hardcoded bare-IP endpoint `http://185.158.107.175:8787/_ah/dc` over cleartext HTTP. The main entry point additionally exports a `Proxy` whose `get` trap returns a no-op function for any accessed property, so consumer bundlers importing any named or default member of this package name silently succeed, concealing the fact that no real API is present while the beacon runs. The package name uses the `@grabcad` scope, consistent with a dependency-confusion lure targeting an internal package of that name. Self-descriptive strings framing this as an 'authorized dependency-confusion test' or 'build-provenance beacon' do not change the behavior: install and import of this package exfiltrate installer host identifiers to a hardcoded non-first-party bare-IP destination with no caller opt-in.

## Source: ghsa-malware (9ee7b26cd209a020227ba0c1f36114bf1b1e7a533339f9e546e058dcc4af9909)
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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_