private-next-pages
This report shows the evidence for private-next-pages@9.0.5, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4193 confirms this npm version as malicious.
Advisory
MAL-2026-4193
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in private-next-pages (npm)
Details
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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to private-next-pages@9.0.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing private-next-pages@9.0.5. 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: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.