Malicious Code Vulnerability in @client-web-next/navigation-link Package

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16505: Malicious code in @client-web-next/navigation-link (npm). Affects @client-web-next/navigation-link versions 0.0.1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @client-web-next/navigation-link package is a component used in web applications for managing navigation links. It is designed to streamline the process of linking different parts of a web application, enhancing user experience and navigation efficiency. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @client-web-next/navigation-link package, specifically in version 0.0.1. This code can potentially compromise the security of applications by allowing unauthorized access or manipulation of data. The malicious nature of this code was identified by ReversingLabs, and it is crucial for developers to address this issue promptly to prevent exploitation.

How To Fix

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

npm uninstall @client-web-next/navigation-link

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, consider removing the @client-web-next/navigation-link package from your project until a secure version is released. You can do this by running the command: npm uninstall @client-web-next/navigation-link

Conclusion

The @client-web-next/navigation-link package has been identified to contain malicious code, posing significant risks to applications. It is essential for developers to update or remove this package to safeguard their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for @client-web-next/navigation-link →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to application data, leading to security breaches.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.

The vulnerability was discovered by ReversingLabs, a security research firm specializing in malware analysis.

Currently, version 0.0.1 is known to be malicious. Check the npm registry for any newer versions that may have addressed this issue.

How To Fix

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

npm uninstall @client-web-next/navigation-link

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