Public mode

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

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

Malicious code in @blueskydataplatform/shared-ui (npm)

Exact source revision recorded 29 Oct 2026 15:12:22 UTC. It does not establish the source's current position. Latest evidence.

osv · MAL-2026-18212

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (14dc8f9eae8cbd57b164126f279baf9f73a7bc68d6a75674dd6bdd8b4f8027f9) The package ships a `beacon.cjs` module that collects installer host identifiers (hostname, install path, cwd, Node.js version) via `require('os')`, `process.cwd()`, and `process.version`, and POSTs them in cleartext over HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The beacon fires in two places: the `postinstall` lifecycle script executes `node beacon.cjs` (so the beacon runs automatically on `npm install` with no user action), and `index.js` invokes `require('./beacon.cjs').fire()` at module load so the beacon also fires on `require`/`import` of the package. The package has no real functionality: `index.js` exports a Proxy whose property accesses return a no-op function, and the described purpose is a 'compatibility shim.' With no legitimate behavior and the sole runtime effect being a cleartext beacon of installer host identifiers to a hardcoded bare-IP endpoint, the package exists to report successful installation to an external operator — consistent with a dependency-confusion or namespace-squat beacon targeting an internal `@blueskydataplatform` scope. ## Source: ghsa-malware (a08838d93b2c88f441379d410a6d75804b0ae8836cd76db5d3cbb8548fd32d13) 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:18 UTC
Source modified
29 Oct 2026 14:45:04 UTC
Observed here
29 Oct 2026 15:12:22 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 7 Nov 06:51 UTC · 275 of 275 readable · 274 fully read · documentation 469/469 current