Malicious Code Vulnerability in no-use-extend-native Package

no-use-extend-native Updated 24 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192825: Malicious code in no-use-extend-native (npm). Affects no-use-extend-native versions 6.9.0 – 6.9.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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The no-use-extend-native package is a utility in the npm ecosystem that is designed to prevent the extension of native objects in JavaScript. This package is often used to enforce best practices in code quality and maintainability. However, it has been found to contain malicious code that can compromise the security of applications that utilize it.

Vulnerability Detail

The vulnerability in the no-use-extend-native package stems from the presence of malicious code that can execute unauthorized actions within an application. This issue was identified in versions 6.9.0 and 6.9.1 of the package. The malicious code can lead to data breaches, unauthorized access, and potential system compromise, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall no-use-extend-native

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 no-use-extend-native package from their project until a secure version is confirmed. This can be done using the command: 'npm uninstall no-use-extend-native'.

Conclusion

The no-use-extend-native package has been identified with a serious vulnerability due to malicious code. It is crucial for users to update to a secure version or remove the package to protect their applications from potential threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for no-use-extend-native →

Share this vulnerability

FAQ

The no-use-extend-native package is an npm utility that helps developers avoid extending native JavaScript objects, promoting better coding practices.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can identify if your application is affected by this vulnerability.

The risks include potential data breaches, unauthorized access to sensitive information, and overall system compromise due to the execution of malicious code.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If immediate updates are not possible, consider removing the package as a temporary measure 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 no-use-extend-native

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