Critical Malicious Code Vulnerability in bucketpdf-test Package

bucketpdf-test Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16251: Malicious code in bucketpdf-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 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 bucketpdf-test package is an npm library designed for handling PDF files in various applications. It offers functionalities such as PDF generation, manipulation, and rendering. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the bucketpdf-test package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or lead to further exploitation of the system. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall bucketpdf-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 bucketpdf-test package and look for alternative libraries that provide similar functionalities without the associated risks. Always validate the integrity of third-party packages before integrating them into your application.

Conclusion

The bucketpdf-test package has been identified as containing malicious code that poses significant security risks. It is crucial for developers to remove this package from their applications and seek alternatives to ensure the safety and integrity of their software.

See every vulnerability recorded for bucketpdf-test →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and execute harmful commands within the application.

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.

No, there is currently no patch available for the bucketpdf-test package. It is advised to remove the package entirely.

You should uninstall the bucketpdf-test package immediately and replace it with a trusted alternative.

Regularly monitor your dependencies using tools like Vulert, and always review the security status of packages before integrating them into your projects.

How To Fix

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

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