Malicious Code Detected in evil-npm-package: A Critical Security Alert

evil-npm-package Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19992: Malicious code in evil-npm-package (npm). Affected versions are not published. 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 'evil-npm-package' is an npm package that is typically used for various functionalities in JavaScript applications. However, it has been identified to contain malicious code, which poses a significant risk to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, and other security issues, making it crucial for developers to be aware of its implications.

Vulnerability Detail

The vulnerability in 'evil-npm-package' stems from the inclusion of malicious code within the package itself. This code can execute harmful actions without the user's consent, potentially compromising the integrity and security of the application. The malicious code was introduced from version 0 and can affect any application that depends on this package, leading to severe ramifications such as data theft or system compromise.

How To Fix

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

npm uninstall evil-npm-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 remove the package from your dependencies by running the following command in your terminal: npm uninstall evil-npm-package. This will help mitigate the risk until a secure version is available.

Conclusion

The discovery of malicious code in 'evil-npm-package' highlights the importance of vigilance in managing dependencies in software projects. Developers should take immediate action to remove this package and monitor their applications for any potential vulnerabilities.

See every vulnerability recorded for evil-npm-package →

Share this vulnerability

FAQ

'evil-npm-package' is an npm package that has been found to contain malicious code, posing a security risk to applications that use it.

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

If you have 'evil-npm-package' installed, you should uninstall it immediately and look for a secure alternative package.

Currently, there is no patched version available for 'evil-npm-package'. It is recommended to remove the package until a secure alternative is found.

Using 'evil-npm-package' can lead to unauthorized access, data breaches, and other security issues, compromising the integrity of your application.

How To Fix

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

npm uninstall evil-npm-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