Critical Malicious Code Vulnerability in test-mal-npm-pkg Package

test-mal-npm-pkg Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192643: Malicious code in test-mal-npm-pkg (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 test-mal-npm-pkg package is an npm package that is typically used for testing purposes in JavaScript applications. It is designed to facilitate the development and testing of npm packages by providing a controlled environment. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the test-mal-npm-pkg package. This code can lead to full compromise of any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that even after the package is removed, there is no guarantee that all traces of the malicious software will be eliminated, posing a significant risk to the integrity and security of affected systems.

How To Fix

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

npm uninstall test-mal-npm-pkg

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

There are no effective workarounds for this vulnerability other than removing the package and rotating sensitive information. It is recommended to monitor your system for any unusual activity after the package has been removed.

Conclusion

The test-mal-npm-pkg package poses a severe security risk due to the embedded malicious code it contains. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for test-mal-npm-pkg →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall test-mal-npm-pkg' and rotate any sensitive information stored on the affected system.

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

Leaving the test-mal-npm-pkg package installed can lead to unauthorized access to sensitive data and full compromise of your system.

No patched version is available for this package as it is inherently malicious. The best course of action is to remove it entirely.

Vulert monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing the package-lock.json file, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall test-mal-npm-pkg

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