Malicious Code Detected in buffgr-xor Package - MAL-2025-16310

buffgr-xor Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16310: Malicious code in buffgr-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 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 buffgr-xor package is an npm library designed for XOR encryption and decryption operations. It is commonly used in applications requiring data obfuscation and security. However, this package has been found to contain malicious code that can compromise the security of applications utilizing it.

Vulnerability Detail

The vulnerability in the buffgr-xor package originates from the inclusion of malicious code that can execute harmful operations on the host system. This can lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability immediately.

How To Fix

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

npm uninstall buffgr-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

If updating the package is not immediately feasible, consider temporarily removing the buffgr-xor package from your project until a secure version is released. You can do this by running: npm uninstall buffgr-xor.

Conclusion

The buffgr-xor package has been identified as containing malicious code that poses a significant security risk. It is crucial for developers to update or remove the package to protect their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for buffgr-xor →

Share this vulnerability

FAQ

The buffgr-xor package is used for XOR encryption and decryption, commonly employed in applications that require data obfuscation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can help identify if your application is affected.

If you cannot update the package, consider removing it from your project until a secure version is available to mitigate the risk.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Using the compromised buffgr-xor package can lead to unauthorized access, data breaches, and other malicious activities that can severely impact your application's security.

Related vulnerabilities

Recent vulnerabilities recorded for buffgr-xor.

How To Fix

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

npm uninstall buffgr-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