Critical Malicious Code Vulnerability in Puppeteer Package

puppeteer Updated 04 Jun 2026

Summary

29/05/2026
CRITICAL
No i
Critical
Not published

MAL-2026-5077: Malicious code in puppeteer (npm). Affects puppeteer versions 25.0.1. 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

Puppeteer is a popular Node.js library that provides a high-level API to control headless Chrome or Chromium browsers over the DevTools Protocol. It is widely used for web scraping, automated testing, and rendering web pages. However, the package has been compromised, leading to a significant security vulnerability that can fully compromise any system running it.

Vulnerability Detail

The vulnerability originates from a malicious code embedded within the Puppeteer package (version 25.0.1). This code can grant an attacker full control over the affected system, allowing them to access sensitive information, including secrets and keys stored on the machine. The presence of this malicious code classifies it under CWE-506, indicating that the product contains code that appears to be malicious in nature. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall puppeteer

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 measure, avoid using the Puppeteer package until it has been confirmed safe. If you must use it, consider running it in a secure, isolated environment to mitigate potential risks.

Conclusion

The Puppeteer package has been compromised with malicious code, posing a serious risk to any system running it. Immediate action is required to remove the affected version and secure sensitive information. Regular monitoring for vulnerabilities is essential to maintain the integrity of your software.

See every vulnerability recorded for puppeteer →

Share this vulnerability

FAQ

Immediately remove the package and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

You can use Puppeteer again once a safe, patched version is released and verified. Always ensure to stay updated with the latest releases.

Related vulnerabilities

Recent vulnerabilities recorded for puppeteer.

How To Fix

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

npm uninstall puppeteer

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