Malicious Code Detected in browser-wrapper Package

browser-wrapper Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16200: Malicious code in browser-wrapper (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 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 browser-wrapper package is a tool used in the npm ecosystem that allows developers to create a browser-like environment for their applications. It is designed to simplify the process of integrating web functionalities into various projects. However, this package has been found to contain malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the browser-wrapper package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and has been identified as a critical security threat that requires immediate attention.

How To Fix

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

npm uninstall browser-wrapper

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, consider removing the browser-wrapper package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall browser-wrapper'. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The discovery of malicious code in the browser-wrapper package highlights the importance of maintaining secure dependencies in software development. Users are urged to take immediate action by updating or removing the affected package to protect their applications from potential threats.

See every vulnerability recorded for browser-wrapper →

Share this vulnerability

FAQ

The browser-wrapper package is an npm tool designed to create a browser-like environment for applications, facilitating the integration of web functionalities.

The malicious code found in the browser-wrapper package can lead to unauthorized access and potential data breaches in applications that utilize it.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file on the Vulert playground, you can determine if your application is affected.

If you cannot update the package right away, it is advisable to uninstall the browser-wrapper package to mitigate the risk of exploitation until a secure version is available.

Regularly check for updates from the package maintainers and consider using tools like Vulert to receive real-time alerts for any vulnerabilities in your dependencies.

How To Fix

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

npm uninstall browser-wrapper

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