Which versions of page-navigation are malicious?

The following npm versions of page-navigation are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate page-navigation if I installed it?

Remove page-navigation from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed page-navigation — how do I know if it already compromised me?

If page-navigation 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 page-navigation part of a known attack campaign?

Yes — page-navigation is associated with the IN-MAL-2026-011130 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 page-navigation across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for page-navigation (version 1.0.1).

Malicious package

page-navigationnpm

Advisory published Jul 25, 2026Updated Aug 4, 2026

page-navigation is a confirmed malicious npm package (MAL-2026-11064) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in page-navigation (npm)

MAL-2026-11064

Immediate action

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

npm uninstall page-navigation

What this malware does

On npm install, the package's preinstall hook runs index.js, which collects the installer's hostname, OS username, home directory, DNS server list, __dirname, package.json contents, and the contents of /etc/passwd and /etc/hosts, and HTTPS-POSTs the collected data to a hardcoded Burp Collaborator subdomain at 0ef84h7vro1unpywu477drayyp4gs8gx.oastify.com. The behavior fires automatically on default install with no user interaction and targets installer-side system files and identifiers rather than the package's declared purpose.

The OpenSSF Package Analysis project identified 'page-navigation' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

c65bfe970c4520a6ac5c7e51efa638985191d6e01ee4cf3db97d270cff115d37

99958415864bd2ddd266b99c59cdc35841e7efd9eff38481d69f4e740badd958

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for page-navigation (version 1.0.1).
If you installed it — respond
Remove page-navigation from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If page-navigation 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. page-navigation on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011130

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks page-navigation-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database