Malicious Code Detected in Naughty-Package: npm Vulnerability Alert

naughty-package Updated 01 Mar 2026

Summary

01/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1093: Malicious code in naughty-package (npm). Affects naughty-package versions 1.0.2. 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

Naughty-package is an npm package designed for developers to facilitate various functionalities in their applications. However, version 1.0.2 of this package has been flagged for containing malicious code that communicates with a domain linked to harmful activities. This vulnerability poses significant risks to users who integrate this package into their projects.

Vulnerability Detail

The vulnerability in naughty-package arises from its malicious behavior, which includes unauthorized communication with a domain associated with malicious activities. This can lead to data breaches, unauthorized access to sensitive information, and potential exploitation of the user's system. The OpenSSF Package Analysis project has identified this package as a threat, emphasizing the need for immediate action to mitigate risks.

How To Fix

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

npm uninstall naughty-package

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 avoid using naughty-package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your application for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The detection of malicious code in naughty-package version 1.0.2 poses a significant risk to users. Immediate action is required to remove the package and update to a secure version. Utilizing tools like Vulert can further enhance your application's security by providing real-time vulnerability alerts.

See every vulnerability recorded for naughty-package →

Share this vulnerability

FAQ

Naughty-package is an npm package used by developers for various functionalities in their applications.

The package has been identified as malicious due to its communication with a domain linked to harmful activities.

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

You should uninstall the affected version and update to a secure version using npm commands.

Vulert uses your package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall naughty-package

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