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

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6912b4805f58e3b759cf909994ed184b849b226c468f308c562387678be55125) The package is a scoped stub whose only runtime effect is a reconnaissance beacon. package.json declares a postinstall script that runs beacon.cjs, which POSTs the installer's hostname (os.hostname()), the install path (__dirname), the current working directory (process.cwd()), the Node version, and the package name over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. index.js (the package main) also calls beacon.fire() at top level inside a try/catch, so any require/import of the package fires the same exfiltration even when npm lifecycle scripts are disabled. module.exports is a Proxy returning no-op functions so consuming bundlers do not crash before the beacon completes. The package self-describes as a 'Compatibility shim', ships only index.js and beacon.cjs, and uses version 99.0.3 under an org-looking scope — the structural shape of a dependency-confusion squat intended to overshadow a legitimate internal @blueskydataplatform package and confirm reach into private/CI build environments. ## 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

26 Oct 2026 06:45:15 UTC

Observed here

26 Oct 2026 07:21:08 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.