Malicious Code Detected in codeval Package - Security Alert

codeval Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17258: Malicious code in codeval (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 codeval package is a Node.js library used for evaluating code snippets. It is designed to provide a safe environment for executing code, making it popular among developers who require dynamic code evaluation. However, recent findings have revealed that the package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the codeval package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall codeval

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 codeval package from your project until a secure version is released. You can do this by executing the command: npm uninstall codeval. Additionally, review your codebase for any dependencies that may rely on this package.

Conclusion

The discovery of malicious code in the codeval package poses a serious threat to users and their applications. It is crucial to stay informed about updates and take necessary actions to protect your systems. Regularly check for vulnerabilities using tools like Vulert to ensure your software remains secure.

See every vulnerability recorded for codeval →

Share this vulnerability

FAQ

The codeval package is a Node.js library designed for evaluating code snippets safely.

The malicious code can lead to unauthorized access and data breaches in applications using the package.

You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Currently, there is no patched version available. Users should monitor for updates and apply them as soon as they are released.

As a temporary measure, consider uninstalling the codeval package and reviewing your codebase for any dependencies that may rely on it.

How To Fix

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

npm uninstall codeval

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