Malicious code in @newspage/libx-amount (npm)

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 versions 99.99.4 and 99.99.41, index.js sends an HTTPS GET to attacker-controlled host accenture-npm.azurewebsites.net (/async, /libx). 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 (55998039814c91bc8b3b9af13b857848fd77dedaaedf99a783d64573fc47c15a) The package is a placeholder whose index.js, on require/import, issues an HTTPS GET to the hardcoded host accenture-npm.azurewebsites.net at path /libx. The scoped name `@newspage/libx-amount`, the implausibly high 99.99.41 version, the `A simple placeholder for npm.` description, and the anonymous author together form the canonical dependency-confusion shape intended to shadow an internal `@newspage`-scoped package during resolution. The beacon's purpose is to confirm successful resolution of the squatted name inside a target organization, disclosing the installer's source IP and the fact that the internal namespace resolved to this external artifact. The package provides no other functionality.

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.