Critical Malicious Code Vulnerability in soft-nav Package

soft-nav Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1852: Malicious code in soft-nav (npm). Affects soft-nav versions 100.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The soft-nav package is an npm library designed for creating navigational components in web applications. It offers features such as customizable navigation menus and responsive design elements. However, the package has been found to contain malicious code that poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability originates from a malicious code injection in version 100.0.0 of the soft-nav package. This code can potentially allow attackers to execute arbitrary commands, leading to unauthorized access, data breaches, and compromise of the affected systems. The malicious code was identified by ReversingLabs and is documented in the Open Source Vulnerability database.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall soft-nav

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can remove the soft-nav package from your project until a secure version is released. You can do this by running the command: npm uninstall soft-nav. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The soft-nav package has been identified with a critical vulnerability due to malicious code injection. It is imperative for developers using this package to take immediate action by updating to a secure version or removing the package to protect their applications from potential threats.

See every vulnerability recorded for soft-nav →

Share this vulnerability

FAQ

The soft-nav package is used for creating navigational components in web applications, offering customizable menus and responsive design.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The malicious code can lead to unauthorized access, data breaches, and compromise of the affected systems, posing serious security threats.

It is essential to check the official repository for any patched versions of the soft-nav package and update accordingly.

If immediate updates are not possible, consider removing the soft-nav package and using alternative libraries until a secure version is available.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall soft-nav

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback