Malicious Code Vulnerability in pentestlyio-testpackage: A Critical Security Threat

pentestlyio-testpackage Updated 24 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192850: Malicious code in pentestlyio-testpackage (npm). Affects pentestlyio-testpackage versions 0.0.1 – 0.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

pentestlyio-testpackage is an npm package designed for testing purposes within the JavaScript ecosystem. It is utilized by developers to facilitate various testing scenarios. However, this package has been identified as containing malicious code, posing significant security risks to applications that incorporate it.

Vulnerability Detail

The vulnerability in pentestlyio-testpackage arises from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can lead to unauthorized access, data breaches, or other malicious activities. The vulnerability is attributed to the package's versions 0.0.1 and 0.0.2, which were flagged by security researchers from ReversingLabs.

How To Fix

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

npm uninstall pentestlyio-testpackage

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 pentestlyio-testpackage altogether and seek alternative packages that provide similar functionality without the associated risks. Additionally, you can implement security measures such as code reviews and dependency scanning to mitigate potential threats.

Conclusion

The discovery of malicious code in pentestlyio-testpackage highlights the importance of vigilant dependency management in software development. Developers should promptly address this vulnerability by removing the affected package and considering alternatives to safeguard their applications.

See every vulnerability recorded for pentestlyio-testpackage →

Share this vulnerability

FAQ

pentestlyio-testpackage is an npm package used for testing purposes in JavaScript applications.

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Remove the affected versions of pentestlyio-testpackage and update to the latest secure version if available.

Yes, consider using other testing packages that do not have known vulnerabilities.

How To Fix

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

npm uninstall pentestlyio-testpackage

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