Which versions of soft-nav are malicious?

The following npm versions of soft-nav are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate soft-nav if I installed it?

Remove soft-nav 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 soft-nav — how do I know if it already compromised me?

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

Yes — soft-nav is associated with the RLMA-2026-01582 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 soft-nav across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for soft-nav (version 100.0.0).

Malicious package

soft-navnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

soft-nav is a confirmed malicious npm package (MAL-2026-1852) that executes malicious code on install (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in soft-nav (npm)

MAL-2026-1852

Immediate action

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

npm uninstall soft-nav

What this malware does

The package soft-nav was found to contain malicious code.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

0277b6b7978060d84913736da2ee68708f1ae569985b2b7c937e42535462c534

1fcb60176234c23b5621ba75433f01363353d1663b1c03a19192296dd09fd913

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for soft-nav (version 100.0.0).
If you installed it — respond
Remove soft-nav 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 soft-nav 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. soft-nav on npm has been identified as a malicious package (version 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01582

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks soft-nav-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