Malicious Code Vulnerability in thread_ppe-test Package

thread_ppe-test Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1867: Malicious code in thread_ppe-test (npm). Affects thread_ppe-test versions 1.0.0. 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 thread_ppe-test package is an npm module designed for testing purposes in multi-threaded environments. It provides developers with tools to simulate and manage threads effectively. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the thread_ppe-test package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was identified in version 1.0.0 of the package, and its origin is linked to a malicious actor who has exploited the npm ecosystem to distribute harmful software.

How To Fix

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

npm uninstall thread_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 thread_ppe-test package and look for other libraries that offer similar features. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The thread_ppe-test package has been identified as containing malicious code that poses a significant threat to applications. It is crucial to uninstall this package and seek alternatives to ensure the security of your software. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for thread_ppe-test →

Share this vulnerability

FAQ

The thread_ppe-test package is an npm module used for testing multi-threaded applications.

The malicious code can lead to unauthorized access and potential data breaches in your application.

You should uninstall the thread_ppe-test package immediately to mitigate any risks.

Yes, consider looking for other npm packages that provide similar multi-threading functionalities without the security risks.

You can use tools like Vulert, which monitors your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

How To Fix

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

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