Critical Malicious Code Vulnerability in dev-test Package

dev-test Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18345: Malicious code in dev-test (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 dev-test package is an npm library commonly used for development and testing purposes in JavaScript applications. It provides various utilities that assist developers in streamlining their testing processes. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the dev-test package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other malicious activities. The vulnerability affects all versions starting from 0, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall dev-test

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 dev-test package from their project until a secure version is released. This can be done by executing the command: 'npm uninstall dev-test'. Alternatively, consider using a different package that offers similar functionality without the associated risks.

Conclusion

The dev-test package has been identified as containing malicious code, which poses a serious threat to applications that utilize it. Users are urged to update or remove the package to safeguard their projects. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for dev-test →

Share this vulnerability

FAQ

The dev-test package is an npm library designed to assist developers with testing and development tasks in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches, posing significant security risks to applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected. Visit the Vulert playground at Vulert Scanner for a quick check without signup.

If immediate updates are not possible, consider removing the dev-test package from your project as a temporary measure until a secure version is available.

Detailed information about this vulnerability can be found on the GitHub repository of the malicious packages project, which documents various security issues in open-source software.

How To Fix

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

npm uninstall dev-test

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