Malicious Code Detected in browserift Package - Security Alert

browserift Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16202: Malicious code in browserift (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The browserift package is an npm library designed for browser-based functionalities, enabling developers to enhance their web applications with various features. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. The presence of such vulnerabilities can lead to unauthorized access, data breaches, and other malicious activities.

Vulnerability Detail

The vulnerability in the browserift package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized data access, manipulation, or even complete takeover of the application environment. The malicious nature of this code makes it imperative for developers to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall browserift

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 browserift package from your project until a secure version is released. You can do this by running the following command: npm uninstall browserift. This will prevent any malicious code from executing in your application.

Conclusion

The discovery of malicious code in the browserift package highlights the importance of maintaining secure dependencies in software development. Developers are urged to take immediate action to update or remove the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for browserift →

Share this vulnerability

FAQ

The browserift package is an npm library that provides various browser-based functionalities for web applications.

The malicious code found in browserift can lead to unauthorized access and manipulation of application data.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you cannot update the package immediately, it is advisable to uninstall it as a temporary measure to avoid potential security risks.

You can visit Vulert at https://vulert.com, which monitors and alerts for open-source vulnerabilities in real-time using just the package-lock.json file.

Related vulnerabilities

Recent vulnerabilities recorded for browserift.

How To Fix

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

npm uninstall browserift

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