Malicious Code Vulnerability in not-remix Package

not-remix Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1804: Malicious code in not-remix (npm). Affects not-remix versions 0.0.1 – 9.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 not-remix package is an npm library designed for specific functionalities in web development. It is utilized by developers to streamline certain processes within their applications. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the not-remix package, specifically in versions 0.0.1, 0.0.2, and 9.0.0. This code can lead to unauthorized access, data breaches, or other harmful actions that could compromise the integrity of applications using this package. The issue was identified by ReversingLabs and is documented in their findings.

How To Fix

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

npm uninstall not-remix

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, users can remove the not-remix package from their project until a secure version is confirmed. This can be done by executing the following command: npm uninstall not-remix. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The not-remix package has been identified to contain malicious code, posing significant risks to users. It is crucial to update to a secure version or remove the package until a fix is confirmed. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for not-remix →

Share this vulnerability

FAQ

The not-remix package is an npm library used in web development for various functionalities. However, it has been identified to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

If you are using versions 0.0.1, 0.0.2, or 9.0.0 of the not-remix package, you should update to the latest version immediately to mitigate the risks.

The vulnerability was discovered by ReversingLabs, a cybersecurity firm specializing in threat detection and analysis.

The malicious code could lead to unauthorized access, data breaches, or other harmful actions that compromise application security.

How To Fix

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

npm uninstall not-remix

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