Critical Malicious Code Vulnerability in bufder-xor Package

bufder-xor Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16264: Malicious code in bufder-xor (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 bufder-xor package is an npm library designed for performing XOR operations on buffers. It is commonly used in applications that require data manipulation and encryption. However, this package has been identified to contain malicious code that can compromise the security of applications utilizing it, making it a significant risk for developers and users alike.

Vulnerability Detail

The vulnerability in the bufder-xor package originates from the inclusion of malicious code that can execute unauthorized actions within the application. This can lead to data breaches, unauthorized access, and potential exploitation of the system. The malicious code was introduced in version 0 and affects all subsequent versions, posing a serious threat to any application that relies on this package.

How To Fix

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

npm uninstall bufder-xor

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 bufder-xor package altogether and implement your own XOR functionality or use a different library that does not have known vulnerabilities.

Conclusion

The bufder-xor package has been identified to contain malicious code, posing a significant risk to applications that utilize it. Developers are advised to remove the package and seek alternatives to ensure the security of their applications. Regular monitoring of dependencies is crucial to mitigate such vulnerabilities.

See every vulnerability recorded for bufder-xor →

Share this vulnerability

FAQ

bufder-xor is an npm package used for performing XOR operations on buffers, often utilized in data manipulation and encryption tasks.

The malicious code can execute unauthorized actions, potentially leading to data breaches and exploitation of the application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

You should remove the bufder-xor package from your project and consider using a secure alternative. Always keep your dependencies updated.

Currently, there is no patched version available. It is recommended to remove the package until a secure alternative is found.

Related vulnerabilities

Recent vulnerabilities recorded for bufder-xor.

How To Fix

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

npm uninstall bufder-xor

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