Malicious Code Vulnerability in pru-lib-ng Package

pru-lib-ng Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1829: Malicious code in pru-lib-ng (npm). Affects pru-lib-ng versions 9.9.9. 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 pru-lib-ng package is a library designed for Node.js applications, providing various utilities for developers. It is widely used in the npm ecosystem due to its ease of integration and functionality. However, this package has been identified to contain malicious code that poses a significant security risk to applications that depend on it.

Vulnerability Detail

This vulnerability originates from a malicious code injection within the pru-lib-ng package, specifically in version 9.9.9. The presence of this code can lead to unauthorized access, data breaches, or other harmful actions within an application. The malicious code can execute arbitrary commands, potentially compromising the integrity and confidentiality of the system using the package.

How To Fix

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

npm uninstall pru-lib-ng

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 remove the pru-lib-ng package from your project until a secure version is released. You can do this by running the following command: npm uninstall pru-lib-ng. Additionally, consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the pru-lib-ng package highlights the importance of regularly monitoring and updating dependencies in software projects. By following the recommended steps to fix the vulnerability and utilizing tools like Vulert, developers can enhance the security of their applications.

See every vulnerability recorded for pru-lib-ng →

Share this vulnerability

FAQ

pru-lib-ng is a Node.js library that offers various utilities for developers, commonly used in npm projects.

The malicious code can execute unauthorized commands, potentially leading to data breaches and compromising your application's security.

If you are using version 9.9.9 of pru-lib-ng, you should uninstall the package and look for a secure alternative or wait for a patched version.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check for vulnerabilities without installation by visiting the Vulert playground.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall pru-lib-ng

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