@newspage/libx-amount@99.99.41
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 7d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17873 confirms this npm version as malicious.
Advisory
MAL-2026-17873
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @newspage/libx-amount (npm)
Details
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.
---
## 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.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The target source makes an automatic network callback when loaded, with no apparent functional need, but it shows no explicit collection of host, user, or credential data. This is an unresolved telemetry risk warranting a warning rather than a publish block.
Static reason
One or more suspicious static signals were detected.
Trigger
A consumer loads index.js, including through package resolution.
Impact
The callback can observe the caller's network address and that the module was loaded; the source does not establish further data collection.
Mechanism
The module calls https.get with a fixed host and path during module evaluation.
AI rationale
The target source makes an automatic network callback when loaded, with no apparent functional need, but it shows no explicit collection of host, user, or credential data. This is an unresolved telemetry risk warranting a warning rather than a publish block.
Evidence
package.jsonindex.js
Network endpoints1
accenture-npm.azurewebsites.net/libx
Independent scan evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for AI warning decision
- package.json defines empty preinstall and postinstall scripts.
- Loading index.js automatically sends an HTTPS request to a fixed callback URL.
- That request does not add explicit host, user, or credential values.
- The investigation file identifies supplemental snapshots as files not shipped in this package.
Evidence against
- The inspected callback has no shown package function that needs the network request.
Behavioral surface
Network
Trivial
Source & flagged code
10 flagged · loading source.lpm-investigation-context/evidence.jsonView file
•Published source reference
High
Network
Independent evidence contains separately hash/SRI-verified related snapshots, not target-shipped files. Inspect their source to assess callback purpose and activation; no verdict is implied.
.lpm-investigation-context/evidence.jsonView on unpkg1{
"kind": "LPM independent investigation evidence; these supplemental snapshots are not files shipped in the target archive.",
"target": {
"name": "@newspage/libx-amount",
"version": "99.99.41",
"integrity": "sha51
High
Ai Review Evidence
The investigation file identifies supplemental snapshots as files not shipped in this package.
.lpm-investigation-context/evidence.jsonView on unpkg · L1package.jsonView file
•Published source reference
High
Findings
8 High3 Medium1 Low
HighNetwork.lpm-investigation-context/evidence.json
HighNetworkpackage.json
HighNetworkindex.js
HighNetwork.lpm-investigation-context/snapshot-0/index.js
HighInstall Time Lifecycle Scriptspackage.json
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidenceindex.js
HighAi Review Evidence.lpm-investigation-context/evidence.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
LowScripts Present
Affected versions and remediation
This report applies to @newspage/libx-amount@99.99.41.
See all versions of @newspage/libx-amount for other recorded verdicts.
- Avoid installing @newspage/libx-amount@99.99.41. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.