Which versions of @newspage/libx-amount are malicious?

The following npm versions of @newspage/libx-amount are flagged malicious: 99.99.4, 99.99.41, 99.99.42. Treat any of these as compromised.

How do I remediate @newspage/libx-amount if I installed it?

@newspage/libx-amount establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @newspage/libx-amount — how do I know if it already compromised me?

If @newspage/libx-amount was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @newspage/libx-amount part of a known attack campaign?

Yes — @newspage/libx-amount is associated with the IN-MAL-2026-021498, IN-MAL-2026-021499, IN-MAL-2026-021496 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @newspage/libx-amount across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @newspage/libx-amount (3 malicious versions).

Malicious package

@newspage/libx-amountnpm

Advisory published Oct 13, 2026Updated Oct 16, 2026

@newspage/libx-amount is a confirmed malicious npm package (MAL-2026-17873) that opens a backdoor for remote access (malicious versions 99.99.4, 99.99.41, 99.99.42). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-17873

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @newspage/libx-amount

What this malware does

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.

Malicious versions

3 flagged

99.99.499.99.4199.99.42

Indicators of compromise (SHA-256)

55998039814c91bc8b3b9af13b857848fd77dedaaedf99a783d64573fc47c15a

8b35057faee3bcd7f2dd81259174d74735b67dcd5ca9beff6e0a6579ec998612

8ddc74f27a6ad03e75bd0e3302b08aea90a3d05c479e249ecf1d8094312134a0

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @newspage/libx-amount (3 malicious versions).
If you installed it — respond
@newspage/libx-amount establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @newspage/libx-amount was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @newspage/libx-amount on npm has been identified as a malicious package (versions 99.99.4, 99.99.41, 99.99.42 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021498IN-MAL-2026-021499IN-MAL-2026-021496

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @newspage/libx-amount-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database