# MAL-2026-17873: Malicious code in @newspage/libx-amount (npm)


- **Type:** Malicious package
- **Package:** `@newspage/libx-amount` (npm)
- **Published:** 13 Oct 2026

## What is MAL-2026-17873?

MAL-2026-17873 is a malicious package in @newspage/libx-amount, published on 13 Oct 2026. 

### Official description

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.

## What should I do about MAL-2026-17873?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17873 is a malicious package: @newspage/libx-amount (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17873/ (Markdown: https://insights.sbomify.com/MAL-2026-17873/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17873

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17873/
Summaries are generated and may contain mistakes; the official description above is the record.