Malicious Code Detected in buffer-xmr Package - Security Alert

buffer-xmr Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16295: Malicious code in buffer-xmr (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The buffer-xmr package is an npm module designed for handling buffer operations in JavaScript applications. It is commonly used for its ability to manage binary data efficiently. However, this package has been found to contain malicious code, which poses a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the buffer-xmr package originates from the inclusion of malicious code that can compromise the integrity and security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue is particularly concerning as it affects all versions starting from 0, making it critical for users to address it promptly.

How To Fix

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

npm uninstall buffer-xmr

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 may consider removing the buffer-xmr package from your project until a secure version is released. You can do this by running: npm uninstall buffer-xmr.

Conclusion

The buffer-xmr package has been identified as containing malicious code, posing a serious security risk to applications. Users are urged to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for buffer-xmr →

Share this vulnerability

FAQ

The buffer-xmr package is an npm module used for managing buffer operations in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using this package.

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

Yes, it is recommended to update to the latest secure version of the buffer-xmr package to mitigate the vulnerability.

If immediate updates are not possible, consider removing the buffer-xmr package from your project as a temporary measure.

Related vulnerabilities

Recent vulnerabilities recorded for buffer-xmr.

How To Fix

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

npm uninstall buffer-xmr

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