MAL-2026-17873 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.

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.