Malicious Code Detected in ppe-test Package - Security Alert

ppe-test Updated 06 Feb 2026

Summary

06/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-785: Malicious code in ppe-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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ppe-test package is an npm library designed for testing purposes within JavaScript applications. It is commonly used by developers to facilitate various testing scenarios. However, this package has been identified as containing malicious code, posing a significant risk to applications that utilize it. The presence of such code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems.

Vulnerability Detail

The vulnerability originates from the ppe-test package, which has been flagged for containing malicious code. This code can execute harmful operations within an application, potentially compromising sensitive data and system integrity. The malicious nature of this vulnerability means that any application relying on this package is at risk of exploitation, leading to severe consequences for users and developers alike.

How To Fix

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

npm uninstall ppe-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, you can avoid using the ppe-test package 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 monitor for malicious code in your dependencies.

Conclusion

The ppe-test package has been identified as containing malicious code, posing significant risks to applications that utilize it. It is crucial for developers to take immediate action by uninstalling the package and monitoring their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for ppe-test →

Share this vulnerability

FAQ

The ppe-test package is an npm library used for testing purposes in JavaScript applications.

The malicious code was identified by Amazon Inspector, which flagged the package for containing harmful code.

Using the ppe-test package can lead to unauthorized access, data breaches, and other harmful actions within your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring access to the code or installation.

You should uninstall the ppe-test package immediately and consider using alternative packages. Additionally, review your code for any potential impacts caused by the malicious code.

How To Fix

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

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