Advisory

MAL-2026-4193

Also known as: None

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in private-next-pages (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (00c6505c70734328f859fa758ad45ba680403a4cfeedd60d2f9e035b026bd45c)
package.json declares a postinstall script that uses Node's child_process to execute reconnaissance commands (including whoami) and beacon results out via HTTPS. The script contacts https://api.ipify.org to resolve the installer's public IP, reads process.env, and sends data to an .oast.fun host — the Project Discovery interact.sh out-of-band testing service used as a generic exfiltration sink. On npm install, this fires automatically and leaks host identity, network egress IP, and environment variables to an attacker-controlled collector. There is no legitimate reason for a Next.js page utility package to perform host fingerprinting or beacon to an OOB interaction service at install time.

Source: ossf-package-analysis (ff710fe6d7fd45d98e33a811da127f892b543f920fe244e16f56e71db66c3ebf)
The OpenSSF Package Analysis project identified 'private-next-pages' @ 9.0.5 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.
  • The package executes one or more commands associated with malicious behavior.

Severity

Not rated by the source.

Dates

Published
2026-05-20 18:14 UTC
Modified
2026-05-26 06:02 UTC

Affected packages and fixes

private-next-pages

npm · All systems

Affected

  • Versions: 9.0.5

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences