Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 274/275 feeds/APIs · 469/469 docs · 9/9 advisories · checked 04:15 UTC Customize Public modeDiscuss ChangeIntel on Discord

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

Exact source revision recorded 24 Oct 2026 13:17:17 UTC. It does not establish the source's current position. Latest evidence.

osv · MAL-2026-18217

Published

--- _-= 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.

Source published
23 Oct 2026 02:05:19 UTC
Source modified
23 Oct 2026 20:30:05 UTC
Observed here
24 Oct 2026 13:17:17 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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 8 Nov 04:15 UTC · 274 of 275 readable · 272 fully read · documentation 469/469 current