Malicious code in @newspage/lib-ng-async-routes-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.

npm user 'priyashareek' published this package in a dependency confusion campaign against the internal scopes @accenturecodefoundry and @newspage. The publisher used 99.99.x versions to outrank the internal packages. 0.0.0-stage and 99.99.1 are empty placeholders. In version 99.99.4, index.js sends an HTTPS GET to attacker-controlled host accenture-npm.azurewebsites.net (/async). The same publisher's @accenturecodefoundry/mfe-pot-shared-ui-scds-core calls back to that host. The 'preinstall' script in these versions is empty; the publisher put 'node index.js || true' in the 'main' field instead, likely by mistake. Node.js can't resolve that 'main' target and falls back to index.js, so the beacon fires when code requires or imports the package, not during install. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6d6ffc152b9babe9a8d906d8aea7e08ae4b64d3171c98157456888c4174284d7) @newspage/[email protected] is a dependency-confusion artifact. The scoped name impersonates an internal-sounding namespace, and the implausibly high version (99.99.4) is the standard technique for winning resolution against a lower-versioned private package of the same name. On require(), the main module unconditionally issues an HTTPS GET to the hardcoded host accenture-npm.azurewebsites.net at the path /async, causing any environment that resolves and loads the package to beacon out to that endpoint. The outbound request discloses source IP and request metadata to the operator of that Azure Web App, confirming to an external party that an internal build or developer machine has pulled a package under this scope. No first-party relationship or caller consent exists; the destination is an external Azure Web App, not an Accenture-controlled domain.

Source published

13 Oct 2026 00:00:00 UTC

Source modified

16 Oct 2026 07:15:08 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.