Critical Malicious Code Vulnerability in pbr-client Package

pbr-client Updated 02 Oct 2025

Summary

08/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5715: Malicious code in pbr-client (npm). Affects pbr-client versions >= 99.99.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 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 pbr-client package is an npm library designed for client-side interactions with a specific backend service. It is commonly used in JavaScript applications to facilitate communication and data exchange. However, this package has been identified to contain embedded malicious code, posing significant security risks to any application that utilizes it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the pbr-client package. This code can compromise the security of any computer where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that simply removing the package may not eliminate all traces of the compromise, as full control of the affected system may have been granted to an external entity.

How To Fix

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

npm uninstall pbr-client

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 isolate the affected application from the network to prevent any potential data exfiltration while you work on removing the package and securing your system.

Conclusion

The pbr-client package has been identified as containing malicious code that poses a significant security risk. It is essential to remove the package immediately and take necessary precautions to secure your system. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for pbr-client →

Share this vulnerability

FAQ

Immediately remove the pbr-client package from your project and rotate any secrets or keys stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

Yes, you can isolate the application from the network to prevent unauthorized access while you address the vulnerability.

Failure to address this vulnerability could lead to unauthorized access to sensitive data, complete system compromise, and potential data breaches.

Detailed information can be found in the vulnerability report on GitHub and other security advisories related to the package.

How To Fix

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

npm uninstall pbr-client

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