Critical Malicious Code Vulnerability in buffer-xkr Package

buffer-xkr Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16294: Malicious code in buffer-xkr (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 buffer-xkr package is an npm library designed for handling binary data in Node.js applications. It provides utilities for manipulating buffers, which are essential for performance-sensitive applications. However, this package has been identified to contain malicious code that could compromise the security of applications utilizing it.

Vulnerability Detail

The vulnerability in the buffer-xkr package stems from the inclusion of malicious code that can execute unauthorized actions within the host application. This code was introduced in version 0 and poses significant risks, including data theft, unauthorized access, and potential system compromise. Users of this package are strongly advised to take immediate action to mitigate these risks.

How To Fix

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

npm uninstall buffer-xkr

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, consider replacing the buffer-xkr package with an alternative library that provides similar functionality without the associated risks. Ensure to review the alternatives for security and reliability before implementation.

Conclusion

The buffer-xkr package has been identified as containing malicious code that poses significant security risks. Users are urged to uninstall the package and consider alternatives to safeguard their applications. Regular monitoring and vulnerability assessments are essential for maintaining application security.

See every vulnerability recorded for buffer-xkr →

Share this vulnerability

FAQ

The buffer-xkr package is used for handling binary data in Node.js applications, providing utilities for buffer manipulation.

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

The malicious code can lead to data theft, unauthorized access to sensitive information, and potential system compromise.

Currently, there is no patch available. Users are advised to uninstall the package until a secure version is released.

If immediate removal is not possible, consider replacing it with a secure alternative and monitor your application for any suspicious activity.

Related vulnerabilities

Recent vulnerabilities recorded for buffer-xkr.

How To Fix

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

npm uninstall buffer-xkr

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